[deployment-guide/comm-rel: 372/727] Updated the Zone Files section introduction.

[Jaromir Hradilek]

commit f745d508cf4ab87ca32082fe2360ff61b2410c34
Author: Jaromir Hradilek <jhradile at redhat.com>
Date:   Mon Aug 16 11:23:33 2010 +0200

    Updated the Zone Files section introduction.

 en-US/The_BIND_DNS_Server.xml |   57 +++++++++++++++++++++++++++++++++++++---
 1 files changed, 52 insertions(+), 5 deletions(-)
---
diff --git a/en-US/The_BIND_DNS_Server.xml b/en-US/The_BIND_DNS_Server.xml
index 09bfbc6..b2b4855 100644
--- a/en-US/The_BIND_DNS_Server.xml
+++ b/en-US/The_BIND_DNS_Server.xml
@@ -1019,17 +1019,64 @@ options {
       <tertiary>zone files</tertiary>
     </indexterm>
     <para>
-      <firstterm>Zone files</firstterm> contain information about a namespace and are stored in the <command>named</command> working directory (<filename>/var/named/</filename>) by default. Each zone file is named according to the <command>file</command> option data in the <command>zone</command> statement, usually in a way that relates to the domain in question and identifies the file as containing zone data, such as <filename>example.com.zone</filename>.
+      As outlined in <xref linkend="s2-bind-introduction-zones" />, zone files contain information about a namespace. They are stored in the <systemitem class="service">named</systemitem> working directory located in <filename class="directory">/var/named/</filename> by default, and each zone file is named according to the <option>file</option> option in the <option>zone</option> statement, usually in a way that relates to the domain in question and identifies the file as containing zone data, such as <filename>example.com.zone</filename>.
     </para>
+    <table id="table-bind-zone-files">
+      <title>The <systemitem class="service">named</systemitem> service zone files</title>
+      <tgroup cols="2">
+        <thead>
+          <row>
+            <entry>
+              Path
+            </entry>
+            <entry>
+              Description
+            </entry>
+          </row>
+        </thead>
+        <tbody>
+          <row>
+            <entry>
+              <filename class="directory">/var/named/</filename>
+            </entry>
+            <entry>
+              The working directory for the <systemitem class="service">named</systemitem> service. The nameserver is <emphasis>not</emphasis> allowed to write to this directory.
+            </entry>
+          </row>
+          <row>
+            <entry>
+              <filename class="directory">/var/named/slaves/</filename>
+            </entry>
+            <entry>
+              The directory for secondary zones. This directory is writable by the <systemitem class="service">named</systemitem> service.
+            </entry>
+          </row>
+          <row>
+            <entry>
+              <filename class="directory">/var/named/dynamic/</filename>
+            </entry>
+            <entry>
+              The directory for other files, such as dynamic DNS (DDNS) zones or managed DNSSEC keys. This directory is writable by the <systemitem class="service">named</systemitem> service.
+
+            </entry>
+          </row>
+          <row>
+            <entry>
+              <filename class="directory">/var/named/data/</filename>
+            </entry>
+            <entry>
+              The directory for various stytistics and debugging files. This directory is writable by the <systemitem class="service">named</systemitem> service.
+            </entry>
+          </row>
+        </tbody>
+      </tgroup>
+    </table>
     <para>
-      Each zone file may contain <firstterm>directives</firstterm> and <firstterm>resource records</firstterm>. Directives tell the nameserver to perform tasks or apply special settings to the zone. Resource records define the parameters of the zone and assign identities to individual hosts. Directives are optional, but resource records are required to provide name service to a zone.
+      A zone file consists of directives and resource records. Directives tell the nameserver to perform tasks or apply special settings to the zone, resource records define the parameters of the zone and assign identities to individual hosts. While the directives are optional, the resource records are required in order to provide name service to a zone.
     </para>
     <para>
       All directives and resource records should be entered on individual lines.
     </para>
-    <para>
-      Comments can be placed after semicolon characters (<command>;</command>) in zone files.
-    </para>
     <section id="s2-bind-zone-directives">
       <title>Zone File Directives</title>
       <indexterm>