Skip to content
This repository was archived by the owner on Aug 13, 2025. It is now read-only.

Commit 02430a7

Browse files
committed
Clarify qname-minimization relaxed in the ARM
Leading underscore in qname confused some users, and it was not documented.
1 parent 6a4e1d3 commit 02430a7

File tree

1 file changed

+10
-4
lines changed

1 file changed

+10
-4
lines changed

doc/arm/reference.rst

Lines changed: 10 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -1392,14 +1392,20 @@ default is used.
13921392
:tags: query
13931393
:short: Controls QNAME minimization behavior in the BIND 9 resolver.
13941394

1395-
This option controls QNAME minimization behavior in the BIND
1396-
resolver. When set to ``strict``, BIND follows the QNAME
1395+
When this is set to ``strict``, BIND follows the QNAME
13971396
minimization algorithm to the letter, as specified in :rfc:`7816`.
1397+
13981398
Setting this option to ``relaxed`` causes BIND to fall back to
13991399
normal (non-minimized) query mode when it receives either NXDOMAIN or
14001400
other unexpected responses (e.g., SERVFAIL, improper zone cut,
1401-
REFUSED) to a minimized query. ``disabled`` disables QNAME
1402-
minimization completely. ``off`` is a synonym for ``disabled``. The current default is ``relaxed``, but it
1401+
REFUSED) to a minimized query. A resolver can use a leading
1402+
underscore, like ``_.example.com``, in an attempt to improve
1403+
interoperability. (See :rfc:`7816` section 3.)
1404+
1405+
``disabled`` disables QNAME minimization completely.
1406+
``off`` is a synonym for ``disabled``.
1407+
1408+
The current default is ``relaxed``, but it
14031409
may be changed to ``strict`` in a future release.
14041410

14051411
.. namedconf:statement:: tkey-gssapi-keytab

0 commit comments

Comments
 (0)