[deployment-guide/comm-rel: 431/727] Corrected the Incremental Zone Transfers (IXFR) section...

Jaromir Hradilek jhradile at fedoraproject.org
Tue Oct 19 13:01:04 UTC 2010


commit cad3deafcf8b0f6a2d176034ddc1efac6908dafa
Author: Jaromir Hradilek <jhradile at redhat.com>
Date:   Thu Aug 19 10:22:36 2010 +0200

    Corrected the Incremental Zone Transfers (IXFR) section...
    
    ...after changing its name from DNS Protocol Enhancements and placing it
    elsewhere.

 en-US/The_BIND_DNS_Server.xml |   31 ++++++++++++++++++-------------
 1 files changed, 18 insertions(+), 13 deletions(-)
---
diff --git a/en-US/The_BIND_DNS_Server.xml b/en-US/The_BIND_DNS_Server.xml
index 9031b9c..f48e389 100644
--- a/en-US/The_BIND_DNS_Server.xml
+++ b/en-US/The_BIND_DNS_Server.xml
@@ -1900,35 +1900,40 @@ ns.icann.org.           12884   IN      A       192.0.34.126
     <para>
       All of the features mentioned are discussed in greater detail in the <citetitle>BIND 9 Administrator Reference Manual</citetitle> referenced in <xref linkend="s2-bind-installed-docs" />.
     </para>
-    <section id="s2-bind-features-protocol">
-      <title>DNS Protocol Enhancements</title>
+    <section id="s2-bind-features-views">
+      <title>Multiple Views</title>
       <indexterm>
         <primary>BIND</primary>
         <secondary>features</secondary>
-        <tertiary>DNS enhancements</tertiary>
+        <tertiary>multiple views</tertiary>
       </indexterm>
       <para>
-        BIND supports Incremental Zone Transfers (IXFR), where a slave nameserver only downloads the updated portions of a zone modified on a master nameserver. The standard transfer process requires that the entire zone be transferred to each slave nameserver for even the smallest change. For very popular domains with very lengthy zone files and many slave nameservers, IXFR makes the notification and update process much less resource-intensive.
+        Through the use of the <command>view</command> statement in <filename>named.conf</filename>, BIND can present different information depending on which network a request originates from.
+      </para>
+      <para>
+        This is primarily used to deny sensitive DNS entries from clients outside of the local network, while allowing queries from clients inside the local network.
       </para>
       <para>
-        Note that IXFR is only available when using <firstterm>dynamic updating</firstterm> to make changes to master zone records. If manually editing zone files to make changes, Automatic Zone Transfer (AXFR) is used. More information on dynamic updating is available in the <citetitle>BIND 9 Administrator Reference Manual</citetitle> referenced in <xref linkend="s2-bind-installed-docs" />.<!-- RHEL5:  . See <xref linkend="s2-bind-installed-docs"/> for more information. -->
+        The <command>view</command> statement uses the <command>match-clients</command> option to match IP addresses or entire networks and give them special options and zone data.
       </para>
     </section>
-    <section id="s2-bind-features-views">
-      <title>Multiple Views</title>
+    <section id="s2-bind-features-ixfr">
+      <title>Incremental Zone Transfers (IXFR)</title>
       <indexterm>
         <primary>BIND</primary>
         <secondary>features</secondary>
-        <tertiary>multiple views</tertiary>
+        <tertiary>Incremental Zone Transfer (IXFR)</tertiary>
       </indexterm>
       <para>
-        Through the use of the <command>view</command> statement in <filename>named.conf</filename>, BIND can present different information depending on which network a request originates from.
-      </para>
-      <para>
-        This is primarily used to deny sensitive DNS entries from clients outside of the local network, while allowing queries from clients inside the local network.
+        <firstterm>Incremental Zone Transfers</firstterm> (<firstterm>IXFR</firstterm>) allow a secondary nameserver to only download the updated portions of a zone modified on a primary nameserver. Compared to the standard transfer process, this makes the notification and update process much more efficient.
       </para>
+      <indexterm>
+        <primary>BIND</primary>
+        <secondary>features</secondary>
+        <tertiary>Automatic Zone Transfer (AXFR)</tertiary>
+      </indexterm>
       <para>
-        The <command>view</command> statement uses the <command>match-clients</command> option to match IP addresses or entire networks and give them special options and zone data.
+        Note that IXFR is only available when using dynamic updating to make changes to master zone records. If manually editing zone files to make changes, <firstterm>Automatic Zone Transfer</firstterm> (<firstterm>AXFR</firstterm>) is used. See <citetitle>BIND 9 Administrator Reference Manual</citetitle> referenced in <xref linkend="s2-bind-installed-docs" /> for more information on this topic.
       </para>
     </section>
     <section id="s2-bind-features-tsig">


More information about the docs-commits mailing list