[nsd-users] nsd-control / addzone / additional parameters
wouter at nlnetlabs.nl
Tue Dec 9 11:48:26 UTC 2014
-----BEGIN PGP SIGNED MESSAGE-----
On 09/12/14 12:13, Oliver Peter wrote:
> Background: We are looking for some additional parameters in
> nsd-control's addzone function. We have hundreds of thousands of
> slave zones on our nameservers (curently PowerDNS), almost each of
> them is individual in term of notify and provide-xfr settings so we
> cannot possibly use the pattern functionality. Needless to say, a
> static nsd.conf does not work either since our customers rely on
> instant DNS updates.
> So, I had a look into the zone.list format and options.c
> (zone_list_zone_insert), from there I see that the format is more
> or less a fixed model and referenced all over the place.
Yes, and it is not stored in the zonelist file. What you can do is
include: "otherfile.conf" in the main nsd.conf file and list the zones
in config files. Then run nsd-control reconfig. That will reread the
entire config file (and its includes), and find the differences with
the currently running config, and then apply the new zone with its
specific configuration settings. So that would, after reading the
entire config, only apply the changes to the running process.
> So the actual question is: How hard would it be to extend nsd's
> journal to take care about more zone specific settings like notify
> and provide-xfr? The pattern method is nice but does not actually
> work for a high number of individual zones with the possibility to
> be changed immediately without reconfiguring the whole daemon.
The actual running daemon process supports adding individual settings
for an individual zone in the interprocess IPC, but the rest of the
code does not.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
-----END PGP SIGNATURE-----
More information about the nsd-users