From: Bert Hubert <bert.hubert@netherlabs.nl>
Date: Tue, 4 Jan 2011 19:57:22 +0000 (+0000)
Subject: when explicitly asking for an NSEC, we should not do a 'relative' pointer to the... 
X-Git-Tag: auth-3.0~441
X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=1419f169c061004b94021fde0658468ac4576228;p=pdns

when explicitly asking for an NSEC, we should not do a 'relative' pointer to the next record but an absolute one. Spotted by Marco Davids.


git-svn-id: svn://svn.powerdns.com/pdns/trunk/pdns@1806 d19b8d6e-7fed-0310-83ef-9ca221ded41b
---

diff --git a/pdns/packethandler.cc b/pdns/packethandler.cc
index 92a4c0109..dcebf8461 100644
--- a/pdns/packethandler.cc
+++ b/pdns/packethandler.cc
@@ -1200,7 +1200,7 @@ DNSPacket *PacketHandler::questionOrRecurse(DNSPacket *p, bool *shouldRecurse)
 
     // this TRUMPS a cname!
     if(p->qtype.getCode() == QType::NSEC && p->d_dnssecOk) {
-      addNSEC(p, r, target, "", 2); // only NSEC please
+      addNSEC(p, r, target, sd.qname, 2); // only NSEC please
       goto sendit;
     }