move older dig +trace explanation to FAQ

diff --git a/pdns/recursordist/docs/appendices/FAQ.rst b/pdns/recursordist/docs/appendices/FAQ.rst
index 74a2e30535ee413b024ea4ce78c7fc64c446bbb8..c38c0d1dfdc25ac494c7bacd91ec35e2b790c30f 100644 (file)
--- a/pdns/recursordist/docs/appendices/FAQ.rst
+++ b/pdns/recursordist/docs/appendices/FAQ.rst
@@ -86,3 +86,7 @@ With versions older than 4.8, there is another detail: after refreshing the root
 For example, in the default setup the root name servers are called ``[a-m].root-servers.net``, so the :program:`Recursor` will resolve the name servers of the ``.net`` domain.
 This is needed to correctly determine zone cuts to be able to decide if the ``.root-servers.net`` domain is DNSSEC protected. Newer versions solve this by querying the needed information top-down.
 
+Starting with version 5.0.0, enabling :ref:`allow-no-rd` allows for queries without the recursion desired bit to be answered from cache.
+Older versions of the ``dig`` program provided by BIND do not set the RD bit causing it to sometimes fail to perform a ``+trace`` when asking a freshly restarted :program:`Recursor` despite the :ref:`allow-no-rd` option being set.
+This is because there is a short while after restarting that the cache has no authoritative data on the root, so it will answer with an NODATA (NOERROR and no answer records) in that period for RD=0 queries.
+For ``dig`` this has been fixed in `BIND 9.15.1 <https://gitlab.isc.org/isc-projects/bind9/-/issues/1028>` by setting the RD bit.
\ No newline at end of file

diff --git a/pdns/recursordist/settings/table.py b/pdns/recursordist/settings/table.py
index 37e630ed0a33dcd9e14d96bc95e8ee7f9a4ccbc2..e16200c7d11e708318c2c1826179766cadfa7704 100644 (file)
--- a/pdns/recursordist/settings/table.py
+++ b/pdns/recursordist/settings/table.py
@@ -203,10 +203,6 @@ Like :ref:`setting-allow-notify-from`, except reading a sequence of `Subnet`_ fr
         'doc' : '''
 Allow ``no recursion desired (RD=0) queries`` to query cache contents.
 If not set (the default), these queries are answered with rcode ``Refused``.
-
-Note that there is a short while after restarting that the cache has no authoritative data on the root,
-so it will answer with an NODATA (NOERROR and no answer records) in that period for RD=0 queries.
-This affects for example older versions of dig when using its +trace option causing it to fail.
  ''',
     'versionadded': '5.0.0'
     },