[nsd-users] tinydns to nsd

richard lucassen mailinglists at lucassen.org
Sat Dec 28 16:02:09 UTC 2019

On Wed, 25 Dec 2019 11:07:49 +0100
Anand Buddhdev <anandb at ripe.net> wrote:

> 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".

The problem is (was) that I used "include:" statements in nsd.conf
to load zone information. Apparently nsd does not reread the include
files upon a SIGHUP. I scripted everything into 1 file and a HUP
rereads the zone info now.


richard lucassen

More information about the nsd-users mailing list