Hello, It seems our NSD secondary has triggered some sort of intermittent bug After several weeks/months of running nsd stops forking with the new zone data. A manual nsd-control transfer or even nsd-control force_transfer won?t work, only restart of nsd solves the problem. The only ?hint? I?ve found is that the nsd xfrd messages stops appearing in the logs (while the notify messages keeps coming). I?ve put the details in this issue https://github.com/NLnetLabs/nsd/issues/417 Re, /P -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 833 bytes Desc: Message signed with OpenPGP URL: <http://lists.nlnetlabs.nl/pipermail/nsd-users/attachments/20241227/3a02474f/attachment.bin>
hi, On 2024-12-27 22:32, Fredrik Pettai via nsd-users wrote:> Hello, > > It seems our NSD secondary has triggered some sort of intermittent bug > After several weeks/months of running nsd stops forking with the new > zone data. > > A manual nsd-control transfer or even nsd-control force_transfer won?t > work, only restart of nsd solves the problem. > The only ?hint? I?ve found is that the nsd xfrd messages stops > appearing in the logs (while the notify messages keeps coming). > > I?ve put the details in this issue > https://github.com/NLnetLabs/nsd/issues/417It seems somewhat similar to the issue I have experienced: https://github.com/NLnetLabs/nsd/issues/338 in my case it recovered on its own. Regards, Tam?s