Displaying 3 results from an estimated 3 matches for "force_transfer".
2024 Dec 28
2
NSD stops forking with newer zone data
...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/417
It see...
2024 Dec 27
1
NSD stops forking with newer zone data
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 -------...
2023 Dec 04
1
Question on slave
...debian).
What I have done is create the whole master config (with all the zones
and notify+provide-xfr fields) and, on the slave, only defined the
"server" part of the config and, for each zone, the allow-notify and
request-xfr fields.
When, on the slave, I execute "nsd-control force_transfer gosane.fr" i
just get an "ok" message.
Then "nsd-control zonestatus gosane.Fr" spits out:
zone:?? gosane.fr
?????? state: ok
?????? served-serial: "2023110103 since 2023-12-04T12:39:04"
?????? commit-serial: "2023110103 since 2023-12-04T12:39:04"
?...