From 4b93ec08055b370f74fdca6ea191728cfae69871 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Ond=C5=99ej=20Sur=C3=BD?= Date: Thu, 27 Jan 2022 12:51:06 +0100 Subject: [PATCH] Fix typo in qname-wait-recurse In the RPZ documentation, there's a mistake where it states that the default behavior will be disabled by setting `qname-wait-recurse yes;` while in fact it's opposite `qname-wait-recurse no;`. This affects only the RST documentation. (cherry picked from commit 1e711dcccbb57c4dd777f7b0206db00a3d86d8b5) --- doc/arm/reference.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/arm/reference.rst b/doc/arm/reference.rst index 736956336d..038962329a 100644 --- a/doc/arm/reference.rst +++ b/doc/arm/reference.rst @@ -4158,7 +4158,7 @@ is listed in a policy zone, to operators of servers for listed names. To prevent that information leak, by default any recursion needed for a request is done before any policy triggers are considered. Because listed domains often have slow authoritative servers, this behavior can -cost significant time. The ``qname-wait-recurse yes`` option overrides +cost significant time. The ``qname-wait-recurse no`` option overrides the default and enables that behavior when recursion cannot change a non-error response. The option does not affect QNAME or client-IP triggers in policy zones listed after other zones containing IP, NSIP,