]> git.ipfire.org Git - thirdparty/bind9.git/commitdiff
3985. [doc] Describe how +ndots and +search interact in dig.
authorMark Andrews <marka@isc.org>
Mon, 20 Oct 2014 21:05:21 +0000 (08:05 +1100)
committerMark Andrews <marka@isc.org>
Mon, 20 Oct 2014 21:05:21 +0000 (08:05 +1100)
                        [RT #37529]

CHANGES
bin/dig/dig.docbook

diff --git a/CHANGES b/CHANGES
index 335daf5b778fa8856553316a9acac8cff97a717a..ae158e6068d3dfde83f459d16830cd3434e1c929 100644 (file)
--- a/CHANGES
+++ b/CHANGES
@@ -1,3 +1,6 @@
+3985.  [doc]           Describe how +ndots and +search interact in dig.
+                       [RT #37529]
+
 3984.  [func]          Accept 256 byte long PINs in native PKCS#11
                        crypto. [RT #37410]
 
index 2726f284e1ceaec872a95c23c4b30355922d33fa..5dfbe212df4cf176ef1abb203e293b7973aef65a 100644 (file)
              are interpreted as relative names and will be searched
              for in the domains listed in the <option>search</option>
              or <option>domain</option> directive in
-             <filename>/etc/resolv.conf</filename>.
+             <filename>/etc/resolv.conf</filename> if
+             <option>+search</option> is set.
            </para>
          </listitem>
        </varlistentry>
              <filename>resolv.conf</filename> (if any).  The search
              list is not used by default.
            </para>
+           <para>
+             'ndots' from <filename>resolv.conf</filename> (default 1)
+              which may be overridden by <parameter>+ndots</parameter>
+             determines if the name will be treated as relative
+             or not and hence whether a search is eventually
+             performed or not.
+           </para>
          </listitem>
        </varlistentry>