[nsd-users] nsd-control / addzone / additional parameters

W.C.A. Wijngaards
Tue, 09 Dec 2014 11:48:26 -0000

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Hi Oliver,

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.

Best regards,
   Wouter

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iQIcBAEBCAAGBQJUhuGKAAoJEJ9vHC1+BF+N0ScQAIGhBF4NphDZcIIzs8gfZ7Fv
G88bjzrkmhzQf5uQkPk4yI7f1HT1NTamC9H3VsCwhsDEFKv4KrwQhgyu40dbdbL3
2eS6IfxoAYHxOYkQYm3o+S84z8eBbHa8xVCKTcMvWJT1iWkmSYQVPSriKBPiUrgp
XLK0YAB2EWR2xXhNf90Ety8ECb1Gq3IOk5n8j8eVY/MOh8hMs0OvWeXb1JfBVIAH
W2hSZoVZTpuasTw6e9OiFvcjV5EU4T81DH2oVisyf2aWm4I1jJhN51HZoQxskL+b
oPNX4Zhqw6sPKK3Gw9Dov0B0iMb7DhTi4kXaTQf8Qv9wivbLlm7PfVQmSyH/sE8U
h3Ei1V+7LsYUL1zKnrTg28JjLmgdMtGHFZmPVnMea6IvgV90M7RjPE5uLe6mWIoj
hyHZyxKdFBci1qvOpPnSrHy3bFD5PfKAnTm2nIrOsU75x+W2tt0ugVni+NIjheEc
gtRXR1MSZl2b4edXrj09bIBlhf1A+PI1BycQR4YqzOcjHw8Nt0kyArHXVwG059aZ
epKFrsMbqPJF1KoUtgmGA5wgHTBgWf9VTUEKabcfnUoVELgIK4gxOFXbnFMVT5MY
vp7ydtId3VuNGQz8Dzkc9ZC9g2cHtNfnVHeHq7O1S1gVF7Fon1hXdHH0VGkruCtp
sHcQrZpnejw/7SVsq2rN
=uZZW
-----END PGP SIGNATURE-----