nsd users - Oct 2017 - nsec3 hash collision

Ok, this has surfaced once again on our slave running NSD 4.1.15

The triggering reason seems to be (remote) master is running Infoblox and the
nsec3 hash collision comes then asking the slave about a  previously deletes
record. I think this was the same senario as in the original case.

I see that 4.1.17 has a "Fix potential null pointer in nsec3 adjustment
tree?.

Should I just upgrade and see if that resolves the issue, or do you want me to
pull some diagnostics out of NSD before?

/P

Hi Fredrik,

Yes that could be a good idea, that fix could already fix your issue.
In case it doesn't, diagnostics from the new version are fine too.

Best regards, Wouter

On 08/10/17 16:02, Fredrik Pettai wrote:
> Ok, this has surfaced once again on our slave running NSD 4.1.15
> 
> The triggering reason seems to be (remote) master is running Infoblox and
the nsec3 hash collision comes then asking the slave about a  previously deletes
record. I think this was the same senario as in the original case.
> 
> I see that 4.1.17 has a "Fix potential null pointer in nsec3
adjustment tree?.
> 
> Should I just upgrade and see if that resolves the issue, or do you want me
to pull some diagnostics out of NSD before?
> 
> /P
> 

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: OpenPGP digital signature
URL:
<http://lists.nlnetlabs.nl/pipermail/nsd-users/attachments/20171009/9f2aa3f3/attachment.bin>