Hi Artur, I agree that the documentation could be a bit clearer. But it is not actually "N seconds after a zone update". It is "every N seconds after starting the server". Setting the value to "1" means that NSD checks for updated zones every second, and writes them to disk.
In most cases, the default of 1 hour works fine. But like you, other people have also been concerned about serving stale zones when NSD is restarted. Some have worked around this by having some kind of pre-stop hook in systemd to call "nsd-control write". There has also been talk about requesting a feature within NSD itself, to write all updated zones before exiting, so that it can work identically regardless of the init system used to run NSD. Regards, Anand On Thu, 20 Mar 2025 at 00:18, Artur <n...@pydo.org> wrote: > Hello Anand, > > Le 19/03/2025 à 23:53, Anand Buddhdev a écrit : > > You can set "zonefiles-write" option in the "server" section to a low > value like "1", which will make NSD write the zone file to disk almost > immediately after an update. > > Yes, it works as expected. Thank you. > > However, the NSD documentation is confusing. It states : "Write updated > secondary zones to their zonefile *every N seconds*." > I would rather say: "Write secondary zones to their zonefiles N seconds > after the zones update." > Or : "Write secondary zone to its zonefile N seconds after the zone > update." > > I don't know if any nsd dev is reading this, but maybe there is an > improvement to the documentation here. > > Thank you Otto for your suggestion too. > > -- > Best regards, > Artur > >
_______________________________________________ nsd-users mailing list nsd-users@lists.nlnetlabs.nl https://lists.nlnetlabs.nl/mailman/listinfo/nsd-users
