Adjust default value of "max-recursion-queries"
Since the queries sent towards root and TLD servers are now included in
the count (as a result of the fix for CVE-2020-8616),
"max-recursion-queries" has a higher chance of being exceeded by
non-attack queries. Increase its default value from 75 to 100.
(cherry picked from commit ab0bf49203)
This commit is contained in:
@@ -3500,7 +3500,7 @@ Tuning
|
||||
``max-recursion-queries``
|
||||
This sets the maximum number of iterative queries that may be sent while
|
||||
servicing a recursive query. If more queries are sent, the recursive
|
||||
query is terminated and returns SERVFAIL. The default is 75.
|
||||
query is terminated and returns SERVFAIL. The default is 100.
|
||||
|
||||
``notify-delay``
|
||||
This sets the delay, in seconds, between sending sets of notify messages for a
|
||||
|
||||
@@ -40,6 +40,12 @@ Feature Changes
|
||||
configuration. A new option 'nsec3param' can be used to set the desired
|
||||
NSEC3 parameters, and will detect collisions when resalting. [GL #1620].
|
||||
|
||||
- Adjust the ``max-recursion-queries`` default from 75 to 100. Since the
|
||||
queries sent towards root and TLD servers are now included in the
|
||||
count (as a result of the fix for CVE-2020-8616), ``max-recursion-queries``
|
||||
has a higher chance of being exceeded by non-attack queries, which is the
|
||||
main reason for increasing its default value. [GL #2305]
|
||||
|
||||
Bug Fixes
|
||||
~~~~~~~~~
|
||||
|
||||
|
||||
Reference in New Issue
Block a user