Hello,

this patch removes obsolete options related to DNS.

It applies on top of Martin^2's patch no. 11.

--
Petr^2 Spacek
From ac6c33e24d9e9bade7291d10dc6109566d260d4b Mon Sep 17 00:00:00 2001
From: Petr Spacek <pspa...@redhat.com>
Date: Thu, 17 Oct 2013 14:49:51 +0200
Subject: [PATCH] Remove obsolete options related to DNS.

---
 src/user_guide/en-US/DNS.xml   | 175 ++++++++---------------------------------
 src/user_guide/en-US/Tools.xml |   6 --
 2 files changed, 34 insertions(+), 147 deletions(-)

diff --git a/src/user_guide/en-US/DNS.xml b/src/user_guide/en-US/DNS.xml
index e4e162db5d5ac0740b47407bced03aea1c0b9f7a..09acfa9161a6b12a00d9b25c284447c7246e1d0e 100644
--- a/src/user_guide/en-US/DNS.xml
+++ b/src/user_guide/en-US/DNS.xml
@@ -101,7 +101,7 @@ _kpasswd._udp IN SRV 0 100 464 ipaserver.example.com.</screen>
         <option>--setup-dns</option> option. If DNS is not configured then, it
         can be configured later using the
         <command>ipa-dns-install</command> command. For example:</para>
-        <screen>[root@ipaserver ~]# ipa-dns-install -p secret --ip-address=10.0.0.1 --no-forwarders [--zone-refresh=60 | --zone-notif]</screen>
+        <screen>[root@ipaserver ~]# ipa-dns-install -p secret --ip-address=10.0.0.1 --no-forwarders</screen>
         <itemizedlist>
             <listitem>
                 <para>
@@ -133,24 +133,6 @@ _kpasswd._udp IN SRV 0 100 464 ipaserver.example.com.</screen>
                 <option>--no-reverse</option> option uses the existing reverse
                 zone rather than creating a new reverse zone.</para>
             </listitem>
-            <listitem>
-                <para>The &IPA; server can actively check to see when new DNS
-                zones are added and to update its DNS server accordingly. If no
-                value is explicitly given, the zone refresh period is 30
-                seconds. The refresh interval can be set to another value using
-                the
-                <option>--zone-refresh</option> option, which sets the polling
-                interval in seconds.</para>
-            </listitem>
-            <listitem>
-                <para>Similar to refreshing the zones, the &IPA; server can
-                leave a persistent search open with its &DS; and capture any
-                new zone changes immediately. This is enabled with the
-                <option>--zone-notif</option> option.</para>
-                <para>If the
-                <option>--zone-notif</option> option is used to configure DNS,
-                then the automatic zone refresh is disabled.</para>
-            </listitem>
         </itemizedlist>
     </section>
     <section id="managing-dnszone-entries">
@@ -228,27 +210,8 @@ _kpasswd._udp IN SRV 0 100 464 ipaserver.example.com.</screen>
                 <para>If the name is not given, the script prompts for it.
                 Other command-line options can also be passed with the
                 <command>ipa dnszone-add</command> command.</para>
-                <para>To add a zone entry:</para>
-                <orderedlist>
-                    <listitem>
-                        <para>Add the new zone. For example:
-                        <screen>[user@ipaserver ~]$ ipa dnszone-add newserver.example.com --admin-email=ad...@example.com --minimum=3000 --dynamic-update</screen></para>
-                    </listitem>
-                    <listitem>
-                        <para>Reload the name service.
-                        <screen>[root@ipaserver ~]# rndc reload</screen></para>
-                        <note>
-                            <title>TIP</title>
-                            <para>To make new resource records immediately
-                            resolvable without restarting the name service,
-                            enable persistent searches with the
-                            <systemitem class="daemon">named</systemitem> service or configure the BIND
-                            service to poll the &DS; automatically for zone
-                            changes. See
-                            <xref linkend="dns-persistent-search" />.</para>
-                        </note>
-                    </listitem>
-                </orderedlist>
+                <para>For example:</para>
+		<para><screen>[user@ipaserver ~]$ ipa dnszone-add newserver.example.com --admin-email=ad...@example.com --minimum=3000 --dynamic-update</screen></para>
             </section>
         </section>
         <section id="modifying-dns-zones">
@@ -697,16 +660,6 @@ Enabled DNS zone "testing.example.com"
             </table>
             <section id="adding-dns-records-ui">
                 <title>Adding DNS Resource Records from the Web UI</title>
-                <note>
-                    <title>TIP</title>
-                    <para>To make new resource records immediately resolvable
-                    without restarting the name service, enable persistent
-                    searches with the
-                    <systemitem class="daemon">named</systemitem> service or
-                    configure the BIND service to poll the &DS; automatically
-                    for zone changes. See
-                    <xref linkend="dns-persistent-search" />.</para>
-                </note>
                 <orderedlist>
                     <listitem>
                         <para>Open the
@@ -1070,16 +1023,6 @@ Enabled DNS zone "testing.example.com"
                 </section>
                 <section id="dnsrecord-add-examples">
                     <title>Examples of Adding DNS Resource Records</title>
-                    <note>
-                        <title>TIP</title>
-                        <para>To make new resource records immediately
-                        resolvable without restarting the name service, enable
-                        persistent searches with the
-                        <systemitem class="daemon">named</systemitem> service or
-                        configure the BIND service to poll the &DS;
-                        automatically for zone changes. See
-                        <xref linkend="dns-persistent-search" />.</para>
-                    </note>
                     <indexterm>
                         <primary>zone records</primary>
                         <secondary>IPv4 example</secondary>
@@ -1361,21 +1304,27 @@ Enabled DNS zone "testing.example.com"
         arg "auth_method sasl";
         arg "sasl_mech GSSAPI";
         arg "sasl_user DNS/server.example.com";
-        };</screen>
+};</screen>
         </example>
         <para>This configuration uses implied default values for
-        <emphasis>other</emphasis> plug-in behaviors, like how long it maintains
-        the cache. The assumed, default configuration can be changed by adding
-        arguments to the
+        <emphasis>other</emphasis> plug-in behavior.
+        Default configuration can be changed by adding arguments to the
         <command>dynamic-db "ipa"</command> entry.</para>
         <screen>arg "<replaceable>argument value</replaceable>";</screen>
-        <para>The additional parameters are listed in
-        <xref linkend="tab.bind-dyndb-ldap-param" />.</para>
+        <para>Some of additional parameters are listed in
+        <xref linkend="tab.bind-dyndb-ldap-param" />.
+        For complete list of parameters please see README file distributed with
+        <package>bind-dyndb-ldap</package> or read
+        <ulink url="http://git.fedorahosted.org/cgit/bind-dyndb-ldap.git/plain/README";>latest README file on-line</ulink>.</para>
+
         <note>
             <title>NOTE</title>
-            <para>Both cache updates and new zone detection can be forced by
-            reloading the name server:</para>
+            <para>You have to reload
+            <systemitem class="daemon">named</systemitem> daemon after each
+            configuration change:
             <screen>[root@ipaserver ~]# rndc reload</screen>
+            Reload also flushes internal caches and
+            forces new zone detection, which can be useful in case of problems.</para>
         </note>
         <table id="tab.bind-dyndb-ldap-param">
             <title>Additional bind-dyndb-ldap Configuration Parameters</title>
@@ -1389,88 +1338,32 @@ Enabled DNS zone "testing.example.com"
                 </thead>
                 <tbody>
                     <row>
-                        <entry>cache_ttl</entry>
-                        <entry>Checks the DNS configuration in the &DS; for new
-                        zones.</entry>
-                        <entry>120 (seconds); this is defined in the
-                        <package>bind-dyndb-ldap</package> plug-in.</entry>
+                        <entry>timeout</entry>
+                        <entry>Specifies timeout (in seconds) of the queries to
+                        the LDAP server. If the LDAP server doesn't respond
+                        before this timeout then lookup is aborted and BIND
+                        returns SERVFAIL. Value "0" means infinite timeout
+                        (no timeout).</entry>
+                        <entry>10 (seconds)</entry>
                     </row>
                     <row>
-                        <entry>zone_refresh</entry>
-                        <entry>Checks frequency, in seconds, that the server
-                        checks the DNS configuration in the &DS; for new
-                        zones.</entry>
-                        <entry>60 (seconds); this is configured by
-                        <command>ipa-dns-install</command>. If this is not set
-                        in the
-                        <filename>/etc/named.conf</filename> file, the
-                        <package>bind-dyndb-ldap</package> plug-in sets this
-                        value to zero (0), which disables zone refresh.</entry>
+                        <entry>reconnect_internal</entry>
+                        <entry>Specifies time (in seconds) after that the
+                        plugin should try to connect to LDAP server again
+                        in case connection was lost and immediate reconnection
+                        failed.</entry>
+                        <entry>60 (seconds)</entry>
                     </row>
                     <row>
-                        <entry>psearch</entry>
-                        <entry>Enables persistent searches for the &DS; so the
-                        BIND service immediately receives an update
-                        notification when a new DNS zone is added.</entry>
+                        <entry>verbose_checks</entry>
+                        <entry>Enables verbose error messages about each
+                        failure in <package>bind-dyndb-ldap</package> internal
+                        checks. This is useful for debugging purposes.</entry>
                         <entry>no</entry>
                     </row>
                 </tbody>
             </tgroup>
         </table>
-        <section id="dns-cache">
-            <title>Changing the DNS Cache Setting</title>
-            <para>To improve DNS performance, it may be necessary to change the
-            cache setting. By default, DNS records are kept in cache and
-            considered valid for 120 seconds. This means that if a DNS record
-            changes, it will not (necessarily) be propagated to the name server
-            for up to 120 seconds. If the &DS; has a high traffic volume or if
-            records do not change frequently, then the cache time can be
-            increased to improve performance by adding the
-            <parameter>cache_ttl</parameter> parameter.</para>
-            <screen>dynamic-db "ipa" { ... arg "cache_ttl 1800"; };</screen>
-        </section>
-        <section id="dns-persistent-search">
-            <title>Enabling Zone Refreshes and Persistent Searches</title>
-            <para>The DNS service receives its information through the
-            <systemitem>bind-dyndb-ldap</systemitem> plug-in. The plug-in
-            resolves only zones which were configured and enabled in the &DS;
-            when the name server started. When the name service restarts, the
-            plug-in reloads its configuration and identifies any new zones or
-            any new resource records.</para>
-            <para>However, the
-            <systemitem>bind-dyndb-ldap</systemitem> plug-in pulls zone and
-            resource record information from the &IPA; LDAP directory, and it
-            is possible to pull information from that directory apart from
-            simply restarting the plug-in. The
-            <systemitem>bind-dyndb-ldap</systemitem> plug-in search for zone
-            changes actively either by refreshing the zone data or by keeping a
-            persistent connection open to the &DS; and immediately catching any
-            changes.</para>
-            <para>Periodically checking for new zones is the same as
-            <emphasis>refreshing</emphasis> the zone configuration. This is set
-            in the
-            <parameter>zone_refresh</parameter> argument.</para>
-            <screen>dynamic-db "ipa" { ... arg "zone_refresh 30"; };</screen>
-            <para>Alternatively, the plug-in can maintain an open connection to
-            the server through a
-            <emphasis>persistent search</emphasis>. Persistent searches provide
-            immediate notification of changes, unlike polling, and maintain a
-            local cache of the configuration data.</para>
-            <note>
-                <title>NOTE</title>
-                <para>A persistent search catches updates both to zones and to
-                zone resource records.</para>
-            </note>
-            <para>Persistent searches are disabled by default but can be
-            enabled in the
-            <parameter>psearch</parameter> argument:</para>
-            <screen>dynamic-db "ipa" { ... arg "psearch yes"; };</screen>
-            <para>Because persistent searches leave an ongoing, open connection
-            with the &DS;, there can be some performance issues. Performance
-            implications are covered in the
-            <ulink url="http://docs.redhat.com/docs/en-US/Red_Hat_Directory_Server/9.0/html/Administration_Guide/persistent-search.html";>
-            &RHDS; &AG;</ulink>.</para>
-        </section>
     </section>
     <section id="changing-forwarder">
         <title>Changing Recursive Queries Against Forwarders</title>
diff --git a/src/user_guide/en-US/Tools.xml b/src/user_guide/en-US/Tools.xml
index be33e6870115b3ae56a832c97a6739b78ec1f90c..78b93566ab241af54a1e917341d76ea04b70cc19 100644
--- a/src/user_guide/en-US/Tools.xml
+++ b/src/user_guide/en-US/Tools.xml
@@ -4355,12 +4355,6 @@ ipa-ca-install
 						--no-reverse
 					</arg>
 					<arg choice="opt">
-						--zone-refresh=<replaceable>seconds</replaceable>
-					</arg>
-					<arg choice="opt">
-						--zone-notif
-					</arg>
-					<arg choice="opt">
 						--zonemgr=<replaceable>email_address</replaceable>
 					</arg>
 					<arg choice="opt">
-- 
1.8.3.1

_______________________________________________
Freeipa-devel mailing list
Freeipa-devel@redhat.com
https://www.redhat.com/mailman/listinfo/freeipa-devel

Reply via email to