]> git.ipfire.org Git - thirdparty/bind9.git/commitdiff
Clarify relationship between ACLs and RPZ
authorMichał Kępień <michal@isc.org>
Mon, 12 Aug 2019 07:46:12 +0000 (09:46 +0200)
committerMichał Kępień <michal@isc.org>
Mon, 12 Aug 2019 07:48:05 +0000 (09:48 +0200)
In the ARM section about RPZ, add text explicitly stating that ACLs take
precedence over RPZ to prevent users from expecting RPZ actions to be
applied to queries coming from clients which are not permitted access to
the resolver by ACLs.

(cherry picked from commit 33bddbb5d18e17e909142c9a01d893da963697a7)

doc/arm/Bv9ARM-book.xml

index fd529df660bd9298a4e11b78397f75a15a3e452d..d3864781ef129a9bad575477a27b16480ab3584f 100644 (file)
@@ -9696,6 +9696,14 @@ deny-answer-aliases { "example.net"; };
            than that is a configuration error.
          </para>
 
+         <para>
+           Rules encoded in response policy zones are processed after
+           <link linkend="access_control">Access Control Lists
+           (ACLs)</link>.  All queries from clients which are not
+           permitted access to the resolver will be answered with a
+           status code of REFUSED, regardless of configured RPZ rules.
+         </para>
+
          <para>
            Five policy triggers can be encoded in RPZ records.
            <variablelist>