Why do queries for NSEC3 records fail to return the NSEC3 record?
This commit is contained in:
17
FAQ.xml
17
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>
|
||||
|
||||
Reference in New Issue
Block a user