Browse Source

[1580] corrected the comment about how to construct the corresponding
wildcard name (the previous one was seemingly copied from the NSEC
counterpart, which is not applicable here).

JINMEI Tatuya 13 years ago
parent
commit
ecb4b75c7b
1 changed files with 5 additions and 5 deletions
  1. 5 5
      src/bin/auth/query.cc

+ 5 - 5
src/bin/auth/query.cc

@@ -192,12 +192,12 @@ Query::addNSEC3NXDOMAINProof(ZoneFinder& finder) {
                        boost::const_pointer_cast<AbstractRRset>(
                        boost::const_pointer_cast<AbstractRRset>(
                        fresult1.next_proof),
                        fresult1.next_proof),
                        dnssec_);
                        dnssec_);
-    // Next, identify the best possible wildcard name that would match
-    // the query name.  It's the longer common suffix with the qname
-    // between the owner and the 'matched' domain of the NSEC3 that
-    // proves NXDOMAIN,prefixed by the wildcard label, "*".
+
+    // Next, construct the wildcard name at the closest encloser, i.e.,
+    // '*' followed by the closest encloser.
     const Name wildname(Name("*").concatenate(
     const Name wildname(Name("*").concatenate(
-               qname_.split(qname_.getLabelCount() - fresult1.closest_labels)));
+               qname_.split(qname_.getLabelCount() -
+                            fresult1.closest_labels)));
     const ZoneFinder::FindNSEC3Result fresult2 =
     const ZoneFinder::FindNSEC3Result fresult2 =
         finder.findNSEC3(wildname, false);
         finder.findNSEC3(wildname, false);
     if (!fresult2.closest_proof) {
     if (!fresult2.closest_proof) {