Re: nsec3 hash collision
Fredrik Pettai <[email protected]>
| Newsgroups | gmane.network.dns.nsd.general |
|---|---|
| Message-ID | <[email protected]> |
> On 6 Feb 2017, at 09:40, W.C.A. Wijngaards <[email protected]> wrote: > > Hi Fredrik, > > Change the nsec3 salt at the zone signer for this zone. Too bad, the RC release of NSD didn’t make it… After bumping NSD and a restart of the daemon, the problem disappeared... [2017-02-07 18:22:08.209] nsd[583]: error: nsec3 hash collision for name=ad.xxxxxx.se. [2017-02-07 18:22:20.967] nsd[25257]: info: zone xxxxxx.se read with success [2017-02-07 18:22:20.967] nsd[25257]: info: rehash of zone xxxxxx.se. with parameters 1 0 10 4b196e0c58c4 … (But at least I have the option to look at the queries now if the issue surface again…) /P _______________________________________________ nsd-users mailing list [email protected] https://open.nlnetlabs.nl/mailman/listinfo/nsd-users