"expected a exact match NSEC3, got a covering record"

[Hauke Lampe]

> 	--- 9.6.1 released ---
> 
> 2607.	[bug]		named could incorrectly delete NSEC3 records for
> 			empty nodes when processing a update request.  
> 			[RT #19749]

I installed 9.6.1 with a cleaned zone and the problem has not reocurred.
Thank you.

> For your information NSEC3 provides no benefit for this zone as it
> has a known structure which can be easily mapped. 

Indeed, I hadn't thought of that. I just wanted to test NSEC3 with
dynamic updates and this RBL zone was an ideal target. It's only queried
by my own servers, so I don't have to worry about resolvers not handling
NSEC3 properly and if anything breaks, it only affects a small part of
spam scoring on the mail gateways.


Hauke.


-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 260 bytes
Desc: OpenPGP digital signature
URL: <https://lists.isc.org/pipermail/bind-users/attachments/20090614/44975006/attachment.bin>