[nsd-users] nsec3 hash collision
pettai at nordu.net
Fri Feb 3 20:40:36 UTC 2017
I noted that one of our name servers slaving customer zones started to spew these messages over and over again:
[2017-02-03 18:16:03.069] nsd: error: nsec3 hash collision for name=ad.xxxxxx.se.
[2017-02-03 18:16:03.078] nsd: error: nsec3 hash collision for name=ad.xxxxxx.se.
[2017-02-03 18:16:03.111] nsd: error: nsec3 hash collision for name=ad.xxxxxx.se.
And it’s filling up the log file very fast...
It’s probably true and perhaps a real problem at the customer side, but does nsd really need to log 20+ lines with this message every second?
I’ve upgraded to nsd 4.1.14 to check if the error (messages) would go away, but doesn’t seem to affect neither the issue, nor the amount of “spam” nsd pushes to the log file…
So, could nsd please not dos itself with these messages? :)
More information about the nsd-users