Re: nsec3 hash collision
"W.C.A. Wijngaards" <[email protected]>
| Newsgroups | gmane.network.dns.nsd.general |
|---|---|
| Message-ID | <[email protected]> |
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 > _______________________________________________ nsd-users mailing list [email protected] https://open.nlnetlabs.nl/mailman/listinfo/nsd-users
signature.asc
(application/pgp-signature, 833 B)
-----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEE7fqj8spObrBWga+On28cLX4EX40FAlnbJZUACgkQn28cLX4E X42z/BAApdeKeuv5flBwfhXeo3C6E1uEsqbWi4RmKXRAQv/IbxXNiJj49xpmtVSF BhXDYQRxrS5iJmjiOOZMA/WpjTinqlnpmYjqflUf0WerismpOFoajLaaiO7vzLKf xf0LCPB2WnFkm2uft3oXDjLDz6RbkyFLk9f/cYIkguFh/BaohE0coSqA8W1Rkl7t sKct7VSqhlGLcjBT/T3+FhpL22bRLHorqYCBNW8TPCdVUKALgEoeeKYWVFwnXull 8KE9xzX8WeqT8UcEOgcewvWM73KhfNyXY/4b9MyvjYG7BeVl72B5JSePh8Ee5lLE C7tT7rWkx77xgkXQzhDHTrJRGndwcYKKD9ZLdBfrZJ1fKNpdo4XOVwOPItLEFBrX aLLbV3VrKqN+3d6vppCWKWofx0axoPo2+12pDwtLZvReZtEEHA3QsxmBeRGN+M1o gKmRT2NckkqRyiQt5bHjyTuCscsfKCb88ai4a2TcsfXV3Y28Xw9IiPMT8lT4Br8M C7dR0+CVjZa8InT2tNeEGT1VfdjcPcZ4F/g0E+USA0S1/SNFsZUW81zu93f9YirR L2EU5pZUXnY7uXdy9cxd/MarJ13ITsRjZGljgxp/gDy4fPSmSP57SfU0h/bDKEY3 A6kmVm1f4ih+58DcPoLxgaqVimDuNi4bnb5F5SIQ4D4NW9lEdTY= =JS3p -----END PGP SIGNATURE-----