Logline and test description updated

diff --git a/pdns/rfc2136handler.cc b/pdns/rfc2136handler.cc
index 02bf313916e619f22146145d87715e9a3fe38bf3..ec81a3a5a788bcabfb07352dc441269483738e35 100755 (executable)
--- a/pdns/rfc2136handler.cc
+++ b/pdns/rfc2136handler.cc
@@ -117,7 +117,7 @@ uint16_t PacketHandler::performUpdate(const string &msgPrefix, const DNSRecord *
     DLOG(L<<msgPrefix<<"Add/Update record (QClass == IN) "<<rrLabel<<"|"<<rrType.getName()<<endl);
 
     if (rrType == QType::NSEC3PARAM) {
-      L<<Logger::Notice<<msgPrefix<<"Setting NSEC3PARAM for zone, resetting ordernames."<<endl;  
+      L<<Logger::Notice<<msgPrefix<<"Setting NSEC3PARAM for zone, resetting ordernames and auth flags."<<endl;  
       NSEC3PARAMRecordContent nsec3param(rr->d_content->getZoneRepresentation(), di->zone);
       d_dk.setNSEC3PARAM(di->zone, nsec3param, (*narrow));
       *haveNSEC3 = d_dk.getNSEC3PARAM(di->zone, ns3pr, narrow);

diff --git a/regression-tests/1dyndns-update-nsec3params/description b/regression-tests/1dyndns-update-nsec3params/description
index 34e272f497cea044815a3b148b2e8c12bc13ef24..d760eead875cb689be85c53cf3f70be01b278cb6 100644 (file)
--- a/regression-tests/1dyndns-update-nsec3params/description
+++ b/regression-tests/1dyndns-update-nsec3params/description
@@ -1,4 +1,4 @@
 We allow to add/remove the NSEC3PARAM record, this test confirms that everything is working correctly.
 The test operates a bit different when in NSEC mode, as we don't add a NSEC3PARAM at the end.
 In NSEC3-NARROW mode, we do add NSEC3PARAM's at the end, but these are then in non-narrow mode as we cannot 
-specify that and the delete of the NSEC3PARAM also removed the narrow flag.
+specify narrow mode in the NSEC3PARAM and the delete of the NSEC3PARAM also removed the narrow flag.