From: JINMEI Tatuya <jinmei@isc.org>
Date: Mon, 18 Jun 2012 23:01:16 +0000 (-0700)
Subject: [2005] explain how ACL rules apply
X-Git-Tag: trac2351_base~226^2~29^2~8
X-Git-Url: http://git.ipfire.org/gitweb.cgi?a=commitdiff_plain;h=5b2f4e7ba0a8c0967719cc9f3e840950ffc7048e;p=thirdparty%2Fkea.git

[2005] explain how ACL rules apply
---

diff --git a/doc/guide/bind10-guide.xml b/doc/guide/bind10-guide.xml
index c65ca8ac93..b0619c5d4d 100644
--- a/doc/guide/bind10-guide.xml
+++ b/doc/guide/bind10-guide.xml
@@ -2141,6 +2141,14 @@ DDNS/zones[0]/update_acl[1]     {"action": "ACCEPT", "from": "::1", "key": "key.
           should have a TSIG key in its constraints.
       </simpara></note>
 
+      <para>
+	The ACL rules will be checked in the listed order, and the
+	first matching one will apply.
+	If none of the rules matches, the default rule will apply,
+	which is rejecting any requests in the case of
+	<command>b10-ddns</command>.
+      </para>
+
       <para>
         Currently update ACL can only control updates per zone basis;
         it's not possible to specify access control with higher