[deployment-guide/comm-rel: 405/727] Updated indexing of the Nameserver Zones section.

[Jaromir Hradilek]

commit 69f5c6b52b6e1d3ae2b9649b3eb6dacab9bb9616
Author: Jaromir Hradilek <jhradile at redhat.com>
Date:   Tue Aug 17 16:00:15 2010 +0200

    Updated indexing of the Nameserver Zones section.

 en-US/The_BIND_DNS_Server.xml |   37 +++++++++++++++++++++++++++++++------
 1 files changed, 31 insertions(+), 6 deletions(-)
---
diff --git a/en-US/The_BIND_DNS_Server.xml b/en-US/The_BIND_DNS_Server.xml
index fcb9b70..7584b00 100644
--- a/en-US/The_BIND_DNS_Server.xml
+++ b/en-US/The_BIND_DNS_Server.xml
@@ -42,8 +42,18 @@
       <title>Nameserver Zones</title>
       <indexterm>
         <primary>BIND</primary>
-        <secondary>zones</secondary>
-        <tertiary>description</tertiary>
+        <secondary>resource record</secondary>
+      </indexterm>
+      <indexterm>
+        <primary>resource record</primary>
+        <see>BIND</see>
+      </indexterm>
+      <indexterm>
+        <primary>fully qualified domain name</primary>
+      </indexterm>
+      <indexterm>
+        <primary><acronym>FQDN</acronym></primary>
+        <see>fully qualified domain name</see>
       </indexterm>
       <para>
         In a DNS server such as BIND, all information is stored in basic data elements called <firstterm>resource records</firstterm> (RR). The resource record is usually a <firstterm>fully qualified domain name</firstterm> (FQDN) of a host, and is broken down into multiple sections organized into a tree-like hierarchy. This hierarchy consists of a main trunk, primary branches, secondary branches, and so on.
@@ -52,9 +62,24 @@
         <title>A simple resource record</title>
         <screen>bob.sales.example.com</screen>
       </example>
+      <indexterm>
+        <primary>BIND</primary>
+        <secondary>zones</secondary>
+        <tertiary>description</tertiary>
+      </indexterm>
       <para>
         Each level of the hierarchy is divided by a period (that is, <literal>.</literal>). In <xref linkend="example-bind-introduction-zones-rr" />, <literal>com</literal> defines the <firstterm>top-level domain</firstterm>, <literal>example</literal> its subdomain, and <literal>sales</literal> the subdomain of <literal>example</literal>. In this case, <literal>bob</literal> identifies a resource record that is part of the <systemitem class="domainname">sales.example.com</systemitem> domain. With the exception of the part furthest to the left (that is, <literal>bob</literal>), each of these sections is called a <firstterm>zone</firstterm> and defines a specific <firstterm>namespace</firstterm>.
       </para>
+      <indexterm>
+        <primary>BIND</primary>
+        <secondary>types</secondary>
+        <tertiary>primary (master) nameserver</tertiary>
+      </indexterm>
+      <indexterm>
+        <primary>BIND</primary>
+        <secondary>types</secondary>
+        <tertiary>secondary (slave) nameserver</tertiary>
+      </indexterm>
       <para>
         Zones are defined on authoritative nameservers through the use of <firstterm>zone files</firstterm>, which contain definitions of the resource records in each zone. Zone files are stored on <firstterm>primary nameservers</firstterm> (also called <firstterm>master nameservers</firstterm>), where changes are made to the files, and <firstterm>secondary nameservers</firstterm> (also called <firstterm>slave nameservers</firstterm>), which receive zone definitions from the primary nameservers. Both primary and secondary nameservers are authoritative for the zone and look the same to clients. Depending on the configuration, any nameserver can also serve as a primary or secondary server for multiple zones at the same time.
       </para>
@@ -70,7 +95,7 @@
             <indexterm>
               <primary>BIND</primary>
               <secondary>types</secondary>
-              <tertiary>authoritative</tertiary>
+              <tertiary>authoritative nameserver</tertiary>
             </indexterm>
             <indexterm>
               <primary>authoritative nameserver</primary>
@@ -79,7 +104,7 @@
             <indexterm>
               <primary>BIND</primary>
               <secondary>types</secondary>
-              <tertiary>primary</tertiary>
+              <tertiary>primary (master) nameserver</tertiary>
             </indexterm>
             <indexterm>
               <primary>primary nameserver</primary>
@@ -88,7 +113,7 @@
             <indexterm>
               <primary>BIND</primary>
               <secondary>types</secondary>
-              <tertiary>secondary</tertiary>
+              <tertiary>secondary (slave) nameserver</tertiary>
             </indexterm>
             <indexterm>
               <primary>secondary nameserver</primary>
@@ -107,7 +132,7 @@
           <indexterm>
             <primary>BIND</primary>
             <secondary>types</secondary>
-            <tertiary>recursive</tertiary>
+            <tertiary>recursive nameserver</tertiary>
           </indexterm>
           <indexterm>
             <primary>recursive nameserver</primary>