]> git.ipfire.org Git - thirdparty/bind9.git/commitdiff
Why do queries for NSEC3 records fail to return the NSEC3 record?
authorMark Andrews <marka@isc.org>
Tue, 9 Sep 2008 05:02:38 +0000 (05:02 +0000)
committerMark Andrews <marka@isc.org>
Tue, 9 Sep 2008 05:02:38 +0000 (05:02 +0000)
FAQ.xml

diff --git a/FAQ.xml b/FAQ.xml
index b944487b2367fc83eecf49f32ff9c24db60f5a91..fb1d3d560e090d85050e136d59be089bbd5ebebd 100644 (file)
--- a/FAQ.xml
+++ b/FAQ.xml
@@ -17,7 +17,7 @@
  - PERFORMANCE OF THIS SOFTWARE.
 -->
 
-<!-- $Id: FAQ.xml,v 1.44 2008/08/27 02:34:48 marka Exp $ -->
+<!-- $Id: FAQ.xml,v 1.45 2008/09/09 05:02:38 marka Exp $ -->
 
 <article class="faq">
   <title>Frequently Asked Questions about BIND 9</title>
@@ -1056,6 +1056,21 @@ empty:
       </answer>
     </qandaentry>
 
+    <qandaentry>
+      <question>
+       <para>
+         Why do queries for NSEC3 records fail to return the NSEC3 record?
+       </para>
+      </question>
+      <answer>
+       <para>
+         NSEC3 records are strictly meta data and can only be returned in
+         the authority section.  This simplifies processing and removes
+         the paradox of a NSEC3 record proving it's own non-existance.
+       </para>
+      </answer>
+    </qandaentry>
+
     </qandadiv> <!-- General Questions -->
     
     <qandadiv><title>Operating-System Specific Questions</title>