[deployment-guide/comm-rel: 392/727] Updated the Example Zone File section.
Jaromir Hradilek
jhradile at fedoraproject.org
Tue Oct 19 12:57:41 UTC 2010
commit 50f80905eac55b4b3820a814fed22dd38e76c81c
Author: Jaromir Hradilek <jhradile at redhat.com>
Date: Mon Aug 16 17:00:43 2010 +0200
Updated the Example Zone File section.
en-US/The_BIND_DNS_Server.xml | 83 ++++++++++++++++++++---------------------
1 files changed, 40 insertions(+), 43 deletions(-)
---
diff --git a/en-US/The_BIND_DNS_Server.xml b/en-US/The_BIND_DNS_Server.xml
index c95fae2..69db5ca 100644
--- a/en-US/The_BIND_DNS_Server.xml
+++ b/en-US/The_BIND_DNS_Server.xml
@@ -1419,11 +1419,11 @@ IN NS dns2.example.com.</screen>
<example id="example-bind-zone-rr-soa">
<title>Using the <command>SOA</command> resource record</title>
<screen>@ 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</screen>
+ 2001062501 ; serial
+ 21600 ; refresh after 6 hours
+ 3600 ; retry after 1 hour
+ 604800 ; expire after 1 week
+ 86400 ) ; minimum TTL of 1 day</screen>
</example>
</listitem>
</varlistentry>
@@ -1449,63 +1449,60 @@ IN NS dns2.example.com.</screen>
<tertiary>zone file examples</tertiary>
</indexterm>
<para>
- Seen individually, directives and resource records can be difficult to grasp. However, when placed together in a single file, they become easier to understand.
+ <xref linkend="example-bind-zone-examples-basic" /> demonstrates a basic usage of standard directives and <command>SOA</command> values.
</para>
- <para>
- The following example shows a very basic zone file.
- </para>
- <screen>$ORIGIN example.com.
+ <example id="example-bind-zone-examples-basic">
+ <title>A sample zone file</title>
+ <screen>$ORIGIN example.com.
$TTL 86400
-@ 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
+@ 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
;
;
- NS dns1.example.com.
- NS dns2.example.com.
-dns1 A 10.0.1.1
- AAAA aaaa:bbbb::1
-dns2 A 10.0.1.2
- AAAA aaaa:bbbb::2
+ NS dns1.example.com.
+ NS dns2.example.com.
+dns1 A 10.0.1.1
+ AAAA aaaa:bbbb::1
+dns2 A 10.0.1.2
+ AAAA aaaa:bbbb::2
;
;
-@ MX 10 mail.example.com.
- MX 20 mail2.example.com.
-mail A 10.0.1.5
- AAAA aaaa:bbbb::5
-mail2 A 10.0.1.6
- AAAA aaaa:bbbb::6
+@ MX 10 mail.example.com.
+ MX 20 mail2.example.com.
+mail A 10.0.1.5
+ AAAA aaaa:bbbb::5
+mail2 A 10.0.1.6
+ AAAA aaaa:bbbb::6
;
;
-; This sample zone file illustrates sharing the same IP addresses for multiple services:
+; This sample zone file illustrates sharing the same IP addresses
+; for multiple services:
;
-services A 10.0.1.10
- AAAA aaaa:bbbb::10
- A 10.0.1.11
- AAAA aaaa:bbbb::11
+services A 10.0.1.10
+ AAAA aaaa:bbbb::10
+ A 10.0.1.11
+ AAAA aaaa:bbbb::11
-ftp CNAME services.example.com.
-www CNAME services.example.com.
+ftp CNAME services.example.com.
+www CNAME services.example.com.
;
;</screen>
+ </example>
<para>
- In this example, standard directives and <command>SOA</command> values are used. The authoritative nameservers are set as <command>dns1.example.com</command> and <command>dns2.example.com</command>, which have <command>A</command> records that tie them to <command>10.0.1.1</command> and <command>10.0.1.2</command>, respectively.
+ In this example, the authoritative nameservers are set as <systemitem class="domainname">dns1.example.com</systemitem> and <systemitem class="domainname">dns2.example.com</systemitem>, and are tied to the <systemitem class="ipaddress">10.0.1.1</systemitem> and <systemitem class="ipaddress">10.0.1.2</systemitem> IP adresses respectively using the <command>A</command> record.
</para>
<para>
- The email servers configured with the <command>MX</command> records point to <command>mail</command> and <command>mail2</command> via <command>A</command> records. Since the <command>mail</command> and <command>mail2</command> names do not end in a trailing period (<command>.</command>), the <command>$ORIGIN</command> domain is placed after them, expanding them to <command>mail.example.com</command> and <command>mail2.example.com</command>. Through the related <command>A</command> resource records, their IP addresses can be determined.
+ The email servers configured with the <command>MX</command> records point to <systemitem class="domainname">mail</systemitem> and <systemitem class="domainname">mail2</systemitem> via <command>A</command> records. Since these names do not end in a trailing period (that is, the <literal>.</literal> character), the <command>$ORIGIN</command> domain is placed after them, expanding them to <systemitem class="domainname">mail.example.com</systemitem> and <systemitem class="domainname">mail2.example.com</systemitem>.
</para>
- <!-- RHEL5: Fix BZ#455162: correct example zone file with regard to records, description
- Note: fixes also applied to certain records in the example zone config above -->
- <!--<para>FTP and Web services, available at the standard <command moreinfo="none">ftp.example.com</command> and <command moreinfo="none">www.example.com</command> names, are pointed at the appropriate servers using <command moreinfo="none">CNAME</command>
- records.</para>-->
<para>
- Services available at the standard names, such as <command>www.example.com</command> (<acronym>WWW</acronym>)<!-- and ftp.example.com (FTP)-->, are pointed at the appropriate servers using a <command>CNAME</command> record.
+ Services available at the standard names, such as <systemitem class="domainname">www.example.com</systemitem> (<acronym>WWW</acronym>), are pointed at the appropriate servers using the <command>CNAME</command> record.
</para>
<para>
- This zone file would be called into service with a <command>zone</command> statement in the <filename>named.conf</filename> similar to the following:
+ This zone file would be called into service with a <command>zone</command> statement in the <filename>/etc/named.conf</filename> similar to the following:
</para>
<screen>zone "example.com" IN {
type master;
More information about the docs-commits
mailing list