[deployment-guide/comm-rel: 357/727] Got rid of the Sample zone Statements subsection.

[Jaromir Hradilek]

commit 1fdd97b9703812129961b0ffcd789252ee7011c4
Author: Jaromir Hradilek <jhradile at redhat.com>
Date:   Fri Aug 13 12:56:50 2010 +0200

    Got rid of the Sample zone Statements subsection.
    
    Instead, I have moved the information under the `zone' statement
    description where it belongs.

 en-US/The_BIND_DNS_Server.xml |   64 ++++++++++++++++++-----------------------
 1 files changed, 28 insertions(+), 36 deletions(-)
---
diff --git a/en-US/The_BIND_DNS_Server.xml b/en-US/The_BIND_DNS_Server.xml
index 2e2896b..170c4a1 100644
--- a/en-US/The_BIND_DNS_Server.xml
+++ b/en-US/The_BIND_DNS_Server.xml
@@ -779,45 +779,37 @@ options {
                 </tbody>
               </tgroup>
             </table>
+            <para>
+              Most changes to the <filename>/etc/named.conf</filename> file of a primary or secondary nameserver involve adding, modifying, or deleting <command>zone</command> statements, and only a small subset of <command>zone</command> statement options is usually needed for a nameserver to work efficiently.
+            </para>
+            <para>
+              In <xref linkend="example-bind-namedconf-common-zone-primary" />, the zone is identified as <literal>example.com</literal>, the type is set to <literal>master</literal>, and the <systemitem class="service">named</systemitem> service is instructed to read the <filename>/var/named/example.com.zone</filename> file. It also allows only a secondary nameserver (<literal>192.168.0.2</literal>) to transfer the zone.
+            </para>
+            <example id="example-bind-namedconf-common-zone-primary">
+              <title>A <command>zone</command> statement for a primary nameserver</title>
+              <screen>zone "example.com" IN {
+  type master;
+  file "example.com.zone";
+  allow-transfer { 192.168.0.2; };
+};</screen>
+            </example>
+            <para>
+              A secondary server's <command>zone</command> statement is slightly different. The type is set to <literal>slave</literal>, and the <literal>masters</literal> directive is telling <command>named</command> the IP address of the master server.
+            </para>
+            <para>
+              In <xref linkend="example-bind-namedconf-common-zone-secondary" />, the <systemitem class="service">named</systemitem> service is configured to query the primary server at the <literal>192.168.0.1</literal> IP address for information about the <literal>example.com</literal> zone. The received information is then saved to the <filename>/var/named/slaves/example.com.zone</filename> file. Note that you have to put all slave zones to <filename>/var/named/slaves</filename> directory, otherwise the service will fail to transfer the zone.
+            </para>
+            <example id="example-bind-namedconf-common-zone-secondary">
+              <title>A <command>zone</command> statement for a secondary nameserver</title>
+              <screen>zone "example.com"{
+  type slave;
+  file "slaves/example.com.zone";
+  masters { 192.168.0.1; };
+};</screen>
+            </example>
           </listitem>
         </varlistentry>
       </variablelist>
-      <section id="s3-bind-configuration-named-zone">
-        <title>Sample <command>zone</command> Statements</title>
-        <indexterm>
-          <primary>BIND</primary>
-          <secondary>configuration of</secondary>
-          <tertiary><command>zone</command> statements sample</tertiary>
-        </indexterm>
-        <para>
-          Most changes to the <filename>/etc/named.conf</filename> file of a master or slave nameserver involves adding, modifying, or deleting <command>zone</command> statements. While these <command>zone</command> statements can contain many options, most nameservers require only a small subset to function efficiently. The following <command>zone</command> statements are very basic examples illustrating a master-slave nameserver relationship.
-        </para>
-        <para>
-          The following is an example of a <command>zone</command> statement for the primary nameserver hosting <command>example.com</command> (<command>192.168.0.1</command>):
-        </para>
-        <screen>zone "example.com" IN {
-type master;
-file "example.com.zone";
-allow-transfer { 192.168.0.2; };
-};</screen>
-        <para>
-          In the statement, the zone is identified as <command>example.com</command>, the type is set to <command>master</command>, and the <command>named</command> service is instructed to read the <filename>/var/named/example.com.zone</filename> file. It also allows only slave nameserver (<command>192.168.0.2</command>) to transfer the zone.
-        </para>
-        <para>
-          A slave server's <command>zone</command> statement for <command>example.com</command> is slightly different from the previous example. For a slave server, the type is set to <command>slave</command> and the <command>masters</command> directive is telling <command>named</command> the IP address of the master server.
-        </para>
-        <para>
-          The following is an example slave server <command>zone</command> statement for <command>example.com</command> zone:
-        </para>
-        <screen>zone "example.com"{
-type slave;
-file "slaves/example.com.zone";
-masters { 192.168.0.1; };
-};</screen>
-        <para>
-          This <command>zone</command> statement configures <command>named</command> on the slave server to query the master server at the <command>192.168.0.1</command> IP address for information about the <command>example.com</command> zone. The information that the slave server receives from the master server is saved to the <filename>/var/named/slaves/example.com.zone</filename> file. Make sure you put all slave zones to <filename>/var/named/slaves</filename> directory otherwise <command>named</command> will fail to transfer the zone.
-        </para>
-      </section>
     </section>
     <section id="s2-bind-namedconf-state-other">
       <title>Other Statement Types</title>