From: Ruben d'Arco Date: Fri, 10 May 2013 15:45:37 +0000 (+0200) Subject: Logline and test description updated X-Git-Tag: rec-3.6.0-rc1~556^2~3^2~39 X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=91ecc3f6159a713f682596fbe8ec0509f80f678f;p=thirdparty%2Fpdns.git Logline and test description updated --- diff --git a/pdns/rfc2136handler.cc b/pdns/rfc2136handler.cc index 02bf313916..ec81a3a5a7 100755 --- a/pdns/rfc2136handler.cc +++ b/pdns/rfc2136handler.cc @@ -117,7 +117,7 @@ uint16_t PacketHandler::performUpdate(const string &msgPrefix, const DNSRecord * DLOG(L<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 34e272f497..d760eead87 100644 --- 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.