[deployment-guide/comm-rel: 393/727] Updated the Reverse Name Resolution Zone Files section.

[Jaromir Hradilek]

commit 60d768850d076679721c537429729c5bcb167730
Author: Jaromir Hradilek <jhradile at redhat.com>
Date:   Mon Aug 16 17:21:53 2010 +0200

    Updated the Reverse Name Resolution Zone Files section.

 en-US/The_BIND_DNS_Server.xml |   49 ++++++++++++++++------------------------
 1 files changed, 20 insertions(+), 29 deletions(-)
---
diff --git a/en-US/The_BIND_DNS_Server.xml b/en-US/The_BIND_DNS_Server.xml
index 69db5ca..85815bc 100644
--- a/en-US/The_BIND_DNS_Server.xml
+++ b/en-US/The_BIND_DNS_Server.xml
@@ -1452,7 +1452,7 @@ IN  NS  dns2.example.com.</screen>
         <xref linkend="example-bind-zone-examples-basic" /> demonstrates a basic usage of standard directives and <command>SOA</command> values.
       </para>
       <example id="example-bind-zone-examples-basic">
-        <title>A sample zone file</title>
+        <title>A simple zone file</title>
         <screen>$ORIGIN example.com.
 $TTL 86400
 @         SOA  dns1.example.com.  hostmaster.example.com. (
@@ -1518,44 +1518,35 @@ www       CNAME  services.example.com.
         <tertiary>reverse name resolution</tertiary>
       </indexterm>
       <para>
-        A reverse name resolution zone file is used to translate an IP address in a particular namespace into an FQDN. It looks very similar to a standard zone file, except that <command>PTR</command> resource records are used to link the IP addresses to a fully qualified domain name.
+        A reverse name resolution zone file is used to translate an IP address in a particular namespace into an fully qualified domain name (FQDN). It looks very similar to a standard zone file, except that the <command>PTR</command> resource records are used to link the IP addresses to a fully qualified domain name as shown in <xref linkend="example-bind-zone-examples-reverse" />.
       </para>
-      <para>
-        The following illustrates the layout of a <command>PTR</command> record:
-      </para>
-      <!-- RHEL5:   ddomingo at redhat.com: above <para>replaces below
-      <para>A <command>PTR</command> record looks similar to this:</para>
- -->
-      <screen>
-        <replaceable>&lt;last-IP-digit&gt;</replaceable> IN PTR <replaceable>&lt;FQDN-of-system&gt;</replaceable></screen>
-      <para>
-        The <replaceable>&lt;last-IP-digit&gt;</replaceable> is the last number in an IP address which points to a particular system's FQDN.
-      </para>
-      <para>
-        In the following example, IP addresses <command>10.0.1.1</command> through <command>10.0.1.6</command> are pointed to corresponding FQDNs. It can be located in <filename>/var/named/example.com.rr.zone</filename>.
-      </para>
-      <!--silas: Fix (BZ#404161): add NS type statement to reverse zone config-->
-      <screen>$ORIGIN 1.0.10.in-addr.arpa.
+      <example id="example-bind-zone-examples-reverse">
+        <title>A reverse name resolution zone file</title>
+        <screen>$ORIGIN 1.0.10.in-addr.arpa.
 $TTL 86400
 @  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
+       2001062501  ; serial
+       21600       ; refresh after 6 hours
+       3600        ; retry after 1 hour
+       604800      ; expire after 1 week
+       86400 )     ; minimum TTL of 1 day
 ;
-@       IN      NS      dns1.example.com.
+@  IN  NS   dns1.example.com.
 ;
 1  IN  PTR  dns1.example.com.
 2  IN  PTR  dns2.example.com.
 ;
-5  IN  PTR    server1.example.com.
-6  IN  PTR    server2.example.com.
+5  IN  PTR  server1.example.com.
+6  IN  PTR  server2.example.com.
 ;
-3  IN  PTR    ftp.example.com.
-4  IN  PTR    ftp.example.com.</screen>
+3  IN  PTR  ftp.example.com.
+4  IN  PTR  ftp.example.com.</screen>
+      </example>
+      <para>
+        In this example, IP addresses <systemitem class="ipaddress">10.0.1.1</systemitem> through <systemitem class="ipaddress">10.0.1.6</systemitem> are pointed to the corresponding fully qualified domain name.
+      </para>
       <para>
-        This zone file would be called into service with a <command>zone</command> statement in the <filename>named.conf</filename> file similar to the following:
+        This zone file would be called into service with a <option>zone</option> statement in the <filename>/etc/named.conf</filename> file similar to the following:
       </para>
       <screen>zone "1.0.10.in-addr.arpa" IN {
   type master;