regen master

diff --git a/doc/arm/Bv9ARM.ch06.html b/doc/arm/Bv9ARM.ch06.html
index 21b6a3652dc2b74a760c1c730ce9c990a08c9ecb..56d1f203b23e988293d2e28490104b114baf30fc 100644 (file)
--- a/doc/arm/Bv9ARM.ch06.html
+++ b/doc/arm/Bv9ARM.ch06.html
@@ -6879,6 +6879,8 @@ deny-answer-aliases { "example.net"; };
             that can be queried normally if allowed.
             It is usually best to restrict those queries with something like
             <span class="command"><strong>allow-query { localhost; };</strong></span>.
+            Note that zones using <span class="command"><strong>masterfile-format map</strong></span>
+            cannot be used as policy zones.
           </p>
 <p>
             A <span class="command"><strong>response-policy</strong></span> option can support

diff --git a/doc/arm/Bv9ARM.ch09.html b/doc/arm/Bv9ARM.ch09.html
index a97b738ee3222be205dc48bf820096eb0cc73c70..ac686818fade3b8ca417e243d291f89de43d9a0f 100644 (file)
--- a/doc/arm/Bv9ARM.ch09.html
+++ b/doc/arm/Bv9ARM.ch09.html
@@ -90,6 +90,11 @@
          were subsequently cached.  This flaw is disclosed
          in CVE-2015-8000. [RT #40987]
        </p></li>
+<li class="listitem"><p>
+         Incorrect reference counting could result in an INSIST
+         failure if a socket error occurred while performing a
+         lookup.  This flaw is disclosed in CVE-2015-8461. [RT#40945]
+       </p></li>
 <li class="listitem"><p>
          An incorrect boundary check in the OPENPGPKEY rdatatype
          could trigger an assertion failure. This flaw is disclosed
@@ -786,6 +791,15 @@
              Negative trust anchors (NTAs) were incorrectly deleted
              when the server was reloaded or reconfigured. [RT #41058]
            </p></li>
+<li class="listitem"><p>
+             Zones configured to use <span class="command"><strong>map</strong></span> format
+             master files can't be used as policy zones because RPZ
+             summary data isn't compiled when such zones are mapped into
+             memory.  This limitation may be fixed in a future release,
+             but in the meantime it has been documented, and attempting
+             to use such zones in <span class="command"><strong>response-policy</strong></span>
+             statements is now a configuration error.  [RT #38321]
+           </p></li>
 </ul></div>
 </li>
 </ul></div>

diff --git a/doc/arm/notes.html b/doc/arm/notes.html
index fb4ff88b209a7840a641eb55c94681a59d8ffbe7..090fca019e4f77605d5e902f90884cad754894f3 100644 (file)
--- a/doc/arm/notes.html
+++ b/doc/arm/notes.html
@@ -51,6 +51,11 @@
          were subsequently cached.  This flaw is disclosed
          in CVE-2015-8000. [RT #40987]
        </p></li>
+<li class="listitem"><p>
+         Incorrect reference counting could result in an INSIST
+         failure if a socket error occurred while performing a
+         lookup.  This flaw is disclosed in CVE-2015-8461. [RT#40945]
+       </p></li>
 <li class="listitem"><p>
          An incorrect boundary check in the OPENPGPKEY rdatatype
          could trigger an assertion failure. This flaw is disclosed
@@ -747,6 +752,15 @@
              Negative trust anchors (NTAs) were incorrectly deleted
              when the server was reloaded or reconfigured. [RT #41058]
            </p></li>
+<li class="listitem"><p>
+             Zones configured to use <span class="command"><strong>map</strong></span> format
+             master files can't be used as policy zones because RPZ
+             summary data isn't compiled when such zones are mapped into
+             memory.  This limitation may be fixed in a future release,
+             but in the meantime it has been documented, and attempting
+             to use such zones in <span class="command"><strong>response-policy</strong></span>
+             statements is now a configuration error.  [RT #38321]
+           </p></li>
 </ul></div>
 </li>
 </ul></div>