From: Otto Moerbeek Date: Mon, 4 Apr 2022 15:27:42 +0000 (+0200) Subject: Docs X-Git-Tag: rec-4.7.0-beta1^2~6 X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=89276babd68d11cdb4eb9aca72e7e1d9b388d8a6;p=thirdparty%2Fpdns.git Docs --- diff --git a/pdns/recursordist/docs/settings.rst b/pdns/recursordist/docs/settings.rst index 5c54e02098..005be69d9c 100644 --- a/pdns/recursordist/docs/settings.rst +++ b/pdns/recursordist/docs/settings.rst @@ -1066,6 +1066,30 @@ Path to a lua file to manipulate the Recursor's answers. See :doc:`lua-scripting The interval between calls to the Lua user defined `maintenance()` function in seconds. See :ref:`hooks-maintenance-callback` +.. _setting-max-busy-dot-probes: + +``max-busy-dot-probes`` +----------------------- +.. versionadded:: 4.7.0 + +- Integer +- Default: 0 + +Limit the maxmium number of simultaneous DoT probes the Recursor will schedule. +The default value 0 means no DoT probes are scheduled. + +DoT probes are used to check if an authoritative server's IP address supports DoT. +If the probe determines an IP address supports DoT, the Recursor will use DoT to contact it for subsequent queries. +The results of probes are remembered and can be viewed by the ``rec_control dump-dot-probe-map`` command. +If the maximum number of pending probes is reached, no probe wil be scheduled, even if no DoT status is known for an address. +If the result of a probe is not yet available, the Recursor will contact the authoritative server in the regular way, +unless an authoritative server is configured to be contacted over DoT always using :ref:`setting-dot-to-auth-names`. +In that case no probe will be scheduled. + +Note:: + DoT probing is an experimental feature. + Please test thoroughly if it is suitable in your specific production environment before enabling. + .. _setting-max-cache-bogus-ttl: ``max-cache-bogus-ttl``