regen

diff --git a/FAQ b/FAQ
index 62a997cf09bd3737f890c073ba0ce143ce7315c6..2c333bef3b24144faaa654ecec08043cd5965717 100644 (file)
--- a/FAQ
+++ b/FAQ
@@ -596,6 +596,13 @@ A: No. The BIND 9 bug database is kept closed for a number of reasons.
    that have been fixed post release. That is as close as we can get to
    providing a bug database.
 
+Q: Why do queries for NSEC3 records fail to return the NSEC3 record?
+
+A: NSEC3 records are strictly meta data and can only be returned in the
+   authority section. This is done so that signing the zone using NSEC3
+   records does not bring names into existance that do not exist in the
+   unsigned version of the zone.
+
 5. Operating-System Specific Questions
 
 5.1. HPUX

diff --git a/FAQ.xml b/FAQ.xml
index ee19b8591aff15bbe125c1f47c9437e5e8ad4cbf..b624d06d534150d12dd662d44f6ee6c11176402d 100644 (file)
--- a/FAQ.xml
+++ b/FAQ.xml
@@ -17,7 +17,7 @@
  - PERFORMANCE OF THIS SOFTWARE.
 -->
 
-<!-- $Id: FAQ.xml,v 1.4.4.23 2008/09/01 02:29:02 tbox Exp $ -->
+<!-- $Id: FAQ.xml,v 1.4.4.24 2008/09/10 01:32:25 tbox Exp $ -->
 
 <article class="faq">
   <title>Frequently Asked Questions about BIND 9</title>
@@ -1056,6 +1056,23 @@ 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 is done so that
+         signing the zone using NSEC3 records does not bring names
+         into existance that do not exist in the unsigned version
+         of the zone.
+       </para>
+      </answer>
+    </qandaentry>
+
     </qandadiv> <!-- General Questions -->
     
     <qandadiv><title>Operating-System Specific Questions</title>