"dump-non-resolving <filename> dump non-resolving nameservers addresses to the named file\n"
"dump-nsspeeds <filename> dump nsspeeds statistics to the named file\n"
"dump-saved-parent-ns-sets <filename>\n"
- " dump saved parent ns sets that were used successfully as fallback\n"
+ " dump saved parent ns sets that were successfully used as fallback\n"
"dump-rpz <zone name> <filename> dump the content of a RPZ zone to the named file\n"
"dump-throttlemap <filename> dump the contents of the throttle map to the named file\n"
"get [key1] [key2] .. get specific statistics\n"
Starting with version 4.7.0, there is a mechanism to save the
parent NS set if it contains *more* names than the child NS set.
-This allows fallback to the saved parent NS set on resolution errors
+This allows falling back to the saved parent NS set on resolution errors
using the child specified NS set.
As experience shows, this configuration error is encountered in the
wild often enough to warrant this workaround.
dump-saved-parent-ns-sets *FILE NAME*
Dump the entries of the map containing saved parent NS sets
- that were used successfully in resolving.
+ that were successfully used in resolving.
The total number of entries is also printed in the header.
- An entry is saved if the recursor sees that parent set includes
+ An entry is saved if the recursor sees that the parent set includes
names not in the child set. This is an indication of a
misconfigured domain.
New settings
^^^^^^^^^^^^
-- The :ref:`settings-save-parent-ns-set` setting has been introduced, enabling fall-back cases if the parent ``NS`` set contains names not in the child ``NS`` set.
+- The :ref:`settings-save-parent-ns-set` setting has been introduced, enabling fallback cases if the parent ``NS`` set contains names not in the child ``NS`` set.
Deprecated and changed settings
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^