rec: allow_no_rd - clarify older dig +trace topples over in case of NODATA

diff --git a/pdns/recursordist/settings/table.py b/pdns/recursordist/settings/table.py
index 4772bbdc56d76714ca40b5550f5a5733c3eb4f57..37e630ed0a33dcd9e14d96bc95e8ee7f9a4ccbc2 100644 (file)
--- a/pdns/recursordist/settings/table.py
+++ b/pdns/recursordist/settings/table.py
@@ -205,8 +205,8 @@ 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
-affecting for example older versions of dig when using its +trace option.
+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'
     },