From 55b8e5104e9cd37c1af4d0508bb3a88c19407ada Mon Sep 17 00:00:00 2001
From: Automatic Updater <source@isc.org>
Date: Wed, 10 Sep 2008 01:43:22 +0000
Subject: [PATCH] regen

---
 FAQ     |  7 +++++++
 FAQ.xml | 19 ++++++++++++++++++-
 2 files changed, 25 insertions(+), 1 deletion(-)

diff --git a/FAQ b/FAQ
index 62a997cf09..2c333bef3b 100644
--- 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 31a4d96629..af60053362 100644
--- a/FAQ.xml
+++ b/FAQ.xml
@@ -17,7 +17,7 @@
  - PERFORMANCE OF THIS SOFTWARE.
 -->
 
-<!-- $Id: FAQ.xml,v 1.30.26.5 2008/09/01 02:40:05 tbox Exp $ -->
+<!-- $Id: FAQ.xml,v 1.30.26.6 2008/09/10 01:43:22 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>