[nsd-users] tinydns to nsd

[Anand Buddhdev]

On 24/12/2019 22:28, richard lucassen via nsd-users wrote:

> OTOH, nsd does not read its config file when receiving a HUP. It would
> be a nice if a USR2 would force a config reload in case of a supervised
> setup. Maybe that's something for the wishlist.

Well, NSD *does* re-read its config file on SIGHUP. However, it only
reapplies those config elements that it can, such as addition or removal
of zones. Other elements, such as the listening address and port, number
of workers (essentially all the elements in the "server" section) cannot
be changed on the fly, so NSD just ignores them. If you change any of
those, you have to restart NSD.

This confuses many users. It would be nice if the developers could
indicate in the nsd.conf man page, which option requires a restart to
take effect, and which one can be adjusted with a "reload" or "reconfig".

Regards,
Anand Buddhdev