[nsd-users] zone addition to running daemon in NSD4

Will Pressly will at edgecast.com
Tue Jan 24 21:01:31 UTC 2012

Hi All,

I am experimenting with NSD4, and am having a little trouble understanding
the workflow for adding a zone to the running daemon with the "nsd-control
addzone <zone name <http://zone.name>> <pattern>" functionality.
Specifically, I am interested in a solution that does not involve zone
transfers. From the man page:

       addzone <zone name> <pattern name>
              Add a new zone to the running server.  The zone is added to
the zonelist file on disk, so it stays after  a  restart.
              The  pattern name determines the options for the new zone.
 For slave zones a zone transfer is immediately attempted.
              For zones with a zonefile, the zone file is attempted to be
read in.

from this information, how do you specify the zonefile for the new, added
zone using a pattern? I tried creating a pattern with the zonefile option
set to the path of the new, added zone -- then invoked the command with the
specified zone and pattern. The problem is that it looks as if the running
daemon cannot be made aware of new patterns specified in the nsd.conf
without a restart of the daemon (as the nsd-control add zone would work if
the daemon was started with the pattern in the nsd.conf, otherwise not).

Am I missing something here? Does anyone have any input on how this
workflow should happen without zone transfers? I think I just haven't fully
connected the dots on this.

Will Pressly, Ph.D.
EdgeCast Networks
will at edgecast.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.nlnetlabs.nl/pipermail/nsd-users/attachments/20120124/51c9787d/attachment.htm>

More information about the nsd-users mailing list