[deployment-guide/comm-rel: 401/727] Various indexing adjustments.

[Jaromir Hradilek]

commit 24172daf68cc036b54f55ee27c580292a2e8ecd7
Author: Jaromir Hradilek <jhradile at redhat.com>
Date:   Tue Aug 17 10:41:38 2010 +0200

    Various indexing adjustments.

 en-US/The_BIND_DNS_Server.xml |   82 +++++++++++++++++++++-------------------
 1 files changed, 43 insertions(+), 39 deletions(-)
---
diff --git a/en-US/The_BIND_DNS_Server.xml b/en-US/The_BIND_DNS_Server.xml
index fb64b1b..6ecfb7d 100644
--- a/en-US/The_BIND_DNS_Server.xml
+++ b/en-US/The_BIND_DNS_Server.xml
@@ -43,7 +43,7 @@
       <indexterm>
         <primary>BIND</primary>
         <secondary>zones</secondary>
-        <tertiary>definition of</tertiary>
+        <tertiary>description</tertiary>
       </indexterm>
       <para>
         In a DNS server such as BIND, all information is stored in basic data elements called <firstterm>resource records</firstterm> (RR). A RR is usually the <firstterm>fully qualified domain name</firstterm> (FQDN) of a host. Resource records are broken down into multiple sections. These sections are organized into a tree-like hierarchy consisting of a main trunk, primary branches, secondary branches, and so forth. Consider the following RR:
@@ -61,48 +61,41 @@
     </section>
     <section id="s2-bind-introduction-nameservers">
       <title>Nameserver Types</title>
-      <indexterm>
-        <primary>BIND</primary>
-        <secondary>types</secondary>
-        <tertiary>authoritative</tertiary>
-      </indexterm>
-      <indexterm>
-        <primary>BIND</primary>
-        <secondary>types</secondary>
-        <tertiary>recursive</tertiary>
-      </indexterm>
-      <indexterm>
-        <primary>BIND</primary>
-        <secondary>types</secondary>
-        <tertiary>primary</tertiary>
-      </indexterm>
-      <indexterm>
-        <primary>BIND</primary>
-        <secondary>types</secondary>
-        <tertiary>secondary</tertiary>
-      </indexterm>
-      <indexterm>
-        <primary>authoritative nameserver</primary>
-        <see>BIND</see>
-      </indexterm>
-      <indexterm>
-        <primary>recursive nameserver</primary>
-        <see>BIND</see>
-      </indexterm>
-      <indexterm>
-        <primary>primary nameserver</primary>
-        <see>BIND</see>
-      </indexterm>
-      <indexterm>
-        <primary>secondary nameserver</primary>
-        <see>BIND</see>
-      </indexterm>
       <para>
         There are two nameserver configuration types:
       </para>
       <variablelist>
         <varlistentry>
-          <term>authoritative</term>
+          <term>
+            <indexterm>
+              <primary>BIND</primary>
+              <secondary>types</secondary>
+              <tertiary>authoritative</tertiary>
+            </indexterm>
+            <indexterm>
+              <primary>authoritative nameserver</primary>
+              <see>BIND</see>
+            </indexterm>
+            <indexterm>
+              <primary>BIND</primary>
+              <secondary>types</secondary>
+              <tertiary>primary</tertiary>
+            </indexterm>
+            <indexterm>
+              <primary>primary nameserver</primary>
+              <see>BIND</see>
+            </indexterm>
+            <indexterm>
+              <primary>BIND</primary>
+              <secondary>types</secondary>
+              <tertiary>secondary</tertiary>
+            </indexterm>
+            <indexterm>
+              <primary>secondary nameserver</primary>
+              <see>BIND</see>
+            </indexterm>
+            authoritative
+          </term>
           <listitem>
             <para>
               Authoritative nameservers answer to resource records that are part of their zones only. This category includes both primary (master) and secondary (slave) nameservers.
@@ -110,7 +103,18 @@
           </listitem>
         </varlistentry>
         <varlistentry>
-          <term>recursive</term>
+          <term>
+          <indexterm>
+            <primary>BIND</primary>
+            <secondary>types</secondary>
+            <tertiary>recursive</tertiary>
+          </indexterm>
+          <indexterm>
+            <primary>recursive nameserver</primary>
+            <see>BIND</see>
+          </indexterm>
+            recursive
+          </term>
           <listitem>
             <para>
               Recursive nameservers offer resolution services, but they are not authoritative for any zone. Answers for all resolutions are cached in a memory for a fixed period of time, which is specified by the retrieved resource record.