[nsd-users] NSD 4 workflow for adding zones on the fly

[Will Pressly]

To add a little more specific information, here is the specific man page
entry I am interested in:
       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.

More simply: I guess the question is, how do we clean out the zonelist
file?

Thanks,
W

On Tue, Jul 3, 2012 at 12:48 PM, Will Pressly <will at edgecast.com> wrote:

> Hi NSD folks,
>
> I had a quick question about NSD 4 and the correct workflow for adding a
> zone to the running daemon. I understand how the addzone works with the
> patterns, and that seems to be working well.
>
> I was just wondering what needs to be done with the /var/db/nsd/zone.list
> file. It seems to accumulate the zone names and related patterns of all
> zones added in this manner. What is the correct process for merging that
> information into the system, and being able to remove the entries in this
> file?
>
> Is it something of the old patch/rebuild flavor of NSD 3.x? Could you
> please give me a pointer on how to make these change more permanent?
>
> Thanks,
> W
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.nlnetlabs.nl/pipermail/nsd-users/attachments/20120703/ca816275/attachment.htm>