diff options
| author | Daniel Baumann <daniel.baumann@progress-linux.org> | 2024-04-07 15:26:00 +0000 |
|---|---|---|
| committer | Daniel Baumann <daniel.baumann@progress-linux.org> | 2024-04-07 15:26:00 +0000 |
| commit | 830407e88f9d40d954356c3754f2647f91d5c06a (patch) | |
| tree | d6a0ece6feea91f3c656166dbaa884ef8a29740e /doc/config-answer-reordering.rst | |
| parent | Initial commit. (diff) | |
| download | knot-resolver-830407e88f9d40d954356c3754f2647f91d5c06a.tar.xz knot-resolver-830407e88f9d40d954356c3754f2647f91d5c06a.zip | |
Adding upstream version 5.6.0.upstream/5.6.0upstream
Signed-off-by: Daniel Baumann <daniel.baumann@progress-linux.org>
Diffstat (limited to 'doc/config-answer-reordering.rst')
| -rw-r--r-- | doc/config-answer-reordering.rst | 17 |
1 files changed, 17 insertions, 0 deletions
diff --git a/doc/config-answer-reordering.rst b/doc/config-answer-reordering.rst new file mode 100644 index 0000000..624e7d4 --- /dev/null +++ b/doc/config-answer-reordering.rst @@ -0,0 +1,17 @@ +.. SPDX-License-Identifier: GPL-3.0-or-later + +Answer reordering +================= +Certain clients are "dumb" and always connect to first IP address or name found +in a DNS answer received from resolver instead of picking randomly. +As a workaround for such broken clients it is possible to randomize +order of records in DNS answers sent by resolver: + +.. function:: reorder_RR([true | false]) + + :param boolean new_value: ``true`` to enable or ``false`` to disable randomization *(optional)* + :return: The (new) value of the option + + If set, resolver will vary the order of resource records within RR sets. + It is enabled by default since 5.3.0. + |