Dear list, I'm a new nsd user. I want to replace a bind9 nameserver, which works as a (bind) slave. I converted the named.conf, started nsd and tested with zonecheck - everything seems okay. Now I want to add additional slave zones to the server. But this works only with stopping and starting the nsd process. None of the other nsdc commands starts the zone transfer from the master. What is wrong? I'm using nsd 3.2.1 (Debian 4.0 amd64) Best regards, Thomas.
On Mon, 16 Feb 2009, Thomas Krause wrote:> Now I want to add additional slave zones to the server. But this works > only with stopping and starting the nsd process. None of the other > nsdc commands starts the zone transfer from the master. > What is wrong?As far as I know, nsd can't add or remove zones while running. This was a feature requested years ago, but I haven't seen any announcements of progress on it. This continues to be the main reason I haven't adopted nsd for production use; I wasn't able to figure out a sane way to add or remove zones without dropping queries. My nameservers handle thousands of domains, and something gets added or removed regularly. I don't want authoritative nameserver downtime every time I do a push. Am I missing something? -- Aaron
On Mon, 16 Feb 2009, Thomas Krause wrote:> I'm a new nsd user. I want to replace a bind9 nameserver, which works as > a (bind) slave. I converted the named.conf, started nsd and tested with > zonecheck - everything seems okay. > Now I want to add additional slave zones to the server. But this works > only with stopping and starting the nsd process. None of the other > nsdc commands starts the zone transfer from the master. > What is wrong? > I'm using nsd 3.2.1 (Debian 4.0 amd64)that's right. Adding/removing zones only take effect after a complete restart, not after a reload. I believe bind behaves similarly. Paul