[deployment-guide/comm-rel: 386/727] Removed the outdated comment.
Jaromir Hradilek
jhradile at fedoraproject.org
Tue Oct 19 12:57:10 UTC 2010
commit 00d47b53ff0ffc7ee35cf1d474a485dff99212b6
Author: Jaromir Hradilek <jhradile at redhat.com>
Date: Mon Aug 16 16:02:52 2010 +0200
Removed the outdated comment.
en-US/The_BIND_DNS_Server.xml | 180 -----------------------------------------
1 files changed, 0 insertions(+), 180 deletions(-)
---
diff --git a/en-US/The_BIND_DNS_Server.xml b/en-US/The_BIND_DNS_Server.xml
index fdaeaab..5b12b79 100644
--- a/en-US/The_BIND_DNS_Server.xml
+++ b/en-US/The_BIND_DNS_Server.xml
@@ -1387,186 +1387,6 @@ IN NS dns2.example.com.</screen>
</listitem>
</varlistentry>
</variablelist>
- <!-- RHEL5: ddomingo at redhat.com: above <variablelist> replaces following <itemizedlist>:
- <itemizedlist>
- <listitem>
- <para><command>A</command> — Address record, which specifies an IP address to assign to a name, as in this example:</para>
-<screen>
-<command><replaceable><host></replaceable> IN A <replaceable><IP-address></replaceable></command>
-</screen>
- <para>If the <replaceable><host></replaceable> value is omitted, then an <command>A</command> record points to a default IP address for the top of the namespace. This system is the target for all non-FQDN requests.</para>
- <para>Consider the following <command>A</command> record examples for the <command>example.com</command> zone file:</para>
-<screen>
-<command> IN A 10.0.1.3 server1 IN A 10.0.1.5</command>
-</screen>
- <para>Requests for <command>example.com</command> are pointed to 10.0.1.3, while requests for <command>server1.example.com</command> are pointed to 10.0.1.5.</para>
- </listitem>
- <listitem>
- <para><command>CNAME</command> — Canonical name record, maps one name to another. This type of record is also known as an alias record.</para>
- <para>The next example tells <command>named</command> that any requests sent to the <replaceable><alias-name></replaceable> should point to the host, <replaceable><real-name></replaceable>.
- <command>CNAME</command> records are most commonly used to point to services that use a common naming scheme, such as <command>www</command> for Web servers.</para>
-<screen>
-<command><replaceable><alias-name></replaceable> IN CNAME <replaceable><real-name></replaceable></command>
-</screen>
- <para>In the following example, an <command>A</command> record binds a hostname to an IP address, while a <command>CNAME</command> record points the commonly used <command>www</command> hostname to it.</para>
-<screen>
-<command>server1 IN A 10.0.1.5 www IN CNAME server1</command>
-</screen>
- </listitem>
- <listitem>
- <para><command>MX</command> — Mail eXchange record, which tells where mail sent to a particular namespace controlled by this zone should go.</para>
-<screen>
-<command> IN MX <replaceable><preference-value></replaceable> <replaceable><email-server-name></replaceable></command>
-</screen>
- <para>In this example, the <replaceable><preference-value></replaceable> allows numerical ranking of the email servers for a namespace, giving preference to some email systems over others. The <command>MX</command> resource record
- with the lowest <replaceable><preference-value></replaceable> is preferred over the others. However, multiple email servers can possess the same value to distribute email traffic evenly among them.</para>
- <para>The <replaceable><email-server-name></replaceable> may be a hostname or FQDN.</para>
-<screen>
-<command> IN MX 10 mail.example.com. IN MX 20 mail2.example.com.</command>
-</screen>
- <para>In this example, the first <command>mail.example.com</command> email server is preferred to the <command>mail2.example.com</command> email server when receiving email destined for the
- <command>example.com</command> domain.</para>
- </listitem>
- <listitem>
- <para><command>NS</command> — NameServer record, which announces the authoritative nameservers for a particular zone.</para>
- <para>This is an example of an <command>NS</command> record:</para>
-<screen>
-<command> IN NS <replaceable><nameserver-name></replaceable></command>
-</screen>
- <para>The <replaceable><nameserver-name></replaceable> should be a FQDN.</para>
- <para>Next, two nameservers are listed as authoritative for the domain. It is not important whether these nameservers are slaves or if one is a master; they are both still considered authoritative.</para>
-<screen>
-<command> IN NS dns1.example.com. IN NS dns2.example.com.</command>
-</screen>
- </listitem>
- <listitem>
- <para><command>PTR</command> — PoinTeR record, designed to point to another part of the namespace.</para>
- <para><command>PTR</command> records are primarily used for reverse name resolution, as they point IP addresses back to a particular name. Refer to <xref linkend="s2-bind-configuration-zone-reverse"/> for more examples of
- <command>PTR</command> records in use.</para>
- </listitem>
- <listitem>
- <para><command>SOA</command> — Start Of Authority resource record, proclaims important authoritative information about a namespace to the nameserver.</para>
- <para>Located after the directives, an <command>SOA</command> resource record is the first resource record in a zone file.</para>
- <para>The following example shows the basic structure of an <command>SOA</command> resource record:</para>
-<screen>
-<command>@ IN SOA <replaceable><primary-name-server></replaceable> <replaceable><hostmaster-email></replaceable> ( <replaceable><serial-number></replaceable> <replaceable><time-to-refresh></replaceable> <replaceable><time-to-retry></replaceable> <replaceable><time-to-expire></replaceable> <replaceable><minimum-TTL> )</replaceable></command>
-</screen>
- <para>The <command>@</command> symbol places the <command>$ORIGIN</command> directive (or the zone's name, if the <command>$ORIGIN</command> directive is not set) as the namespace being defined by this
- <command>SOA</command> resource record. The hostname of the primary nameserver that is authoritative for this domain is the <replaceable><primary-name-server></replaceable> directive, and the email of the person to contact
- about this namespace is the <replaceable><hostmaster-email></replaceable> directive.</para>
- <para>The <replaceable><serial-number></replaceable> directive is a numerical value incremented every time the zone file is altered to indicate it is time for <command>named</command> to reload the zone. The <replaceable><time-to-refresh></replaceable> directive is the numerical value slave servers use to determine how long to wait before asking the master nameserver if any changes have been made to the zone. The <replaceable><serial-number></replaceable>
- directive is a numerical value used by the slave servers to determine if it is using outdated zone data and should therefore refresh it.</para>
- <para>The <replaceable><time-to-retry></replaceable> directive is a numerical value used by slave servers to determine the length of time to wait before issuing a refresh request in the event the master nameserver is not answering. If the master
- has not replied to a refresh request before the amount of time specified in the <replaceable><time-to-expire></replaceable> directive elapses, the slave servers stop responding as an authority for requests concerning that namespace.</para>
- <para>The <replaceable><minimum-TTL></replaceable> directive is the quantity of time other nameservers cache the zone's information.</para>
- <para>When configuring BIND, all times are specified in seconds. However, it is possible to use abbreviations when specifying units of time other than seconds, such as minutes (<command>M</command>), hours
- (<command>H</command>), days (<command>D</command>), and weeks (<command>W</command>). The table in <xref linkend="tb-bind-seconds"/> shows an amount of time in seconds and the equivalent time in
- another format.</para>
- <table id="tb-bind-seconds">
- <title>Seconds compared to other time units</title>
- <tgroup cols="2">
- <colspec colnum="1" colname="seconds" colwidth="50*"></colspec>
- <colspec colnum="2" colname="other" colwidth="50*"></colspec>
- <thead><row>
- <entry>
- Seconds
- </entry>
- <entry>
- Other Time Units
- </entry>
- </row>
- </thead>
- <tbody>
- <row>
- <entry>
- <command>60</command>
- </entry>
- <entry>
- <command>1M</command>
- </entry>
- </row>
- <row>
- <entry>
- <command>1800</command>
- </entry>
- <entry>
- <command>30M</command>
- </entry>
- </row>
- <row>
- <entry>
- <command>3600</command>
- </entry>
- <entry>
- <command>1H</command>
- </entry>
- </row>
- <row>
- <entry>
- <command>10800</command>
- </entry>
- <entry>
- <command>3H</command>
- </entry>
- </row>
- <row>
- <entry>
- <command>21600</command>
- </entry>
- <entry>
- <command>6H</command>
- </entry>
- </row>
- <row>
- <entry>
- <command>43200</command>
- </entry>
- <entry>
- <command>12H</command>
- </entry>
- </row>
- <row>
- <entry>
- <command>86400</command>
- </entry>
- <entry>
- <command>1D</command>
- </entry>
- </row>
- <row>
- <entry>
- <command>259200</command>
- </entry>
- <entry>
- <command>3D</command>
- </entry>
- </row>
- <row>
- <entry>
- <command>604800</command>
- </entry>
- <entry>
- <command>1W</command>
- </entry>
- </row>
- <row>
- <entry>
- <command>31536000</command>
- </entry>
- <entry>
- <command>365D</command>
- </entry>
- </row>
- </tbody>
- </tgroup>
- </table>
- <para>The following example illustrates the form an <command>SOA</command> resource record might take when it is populated with real values.</para>
-<screen>
-<command> @ IN SOA dns1.example.com. hostmaster.example.com. ( 2001062501 ; serial 21600 ; refresh after 6 hours 3600 ; retry after 1 hour 604800 ; expire after 1 week 86400 ) ; minimum TTL of 1 day</command>
-</screen>
- </listitem>
- </itemizedlist>
- -->
</section>
<section id="s2-bind-zone-examples">
<title>Example Zone File</title>
More information about the docs-commits
mailing list