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

[W.C.A. Wijngaards]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi Will,

delzone, that removes the zone from the running server, and also from
the zonelist file (for after a restart).  Old entries are marked as
deleted (for speed) in the zonelist file, space is reused in the file,
and if unused space becomes too big NSD4 writes an entire new file.

So, you have to do nothing.  The zonelist file contains the list of
added zones (and some deleted zones where space is not reclaimed)

The nsd-control delzone zonenname command removes the zone.

If you think you may add it again, use nsd-control write zonename to
write its contents (if changed for slave zones) to a zonefile (if you
configured a zonefile path at all), so you could add it again if you
change your mind.  (if you did not configure a zonefile path, you can
change the pattern in nsd.conf and do nsd-control repattern to change
configuration).

There is no nsd rebuild : with nsd-control reload it will scan for
modified (timestamps on) zonefiles and read them.  You can also force
it to read a specific zone.

Best regards,
   Wouter

On 07/03/2012 10:05 PM, Will Pressly wrote:
> 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 
> <mailto: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
> 
> 


-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.18 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQIcBAEBAgAGBQJP8/uUAAoJEJ9vHC1+BF+No2EQAJXVCluN0L3OeKLnl6ABkaTX
rY6yCOSEZ0r10NDgSyzJgM2gKTlN+OdkcOtUwNxqsENESGwrNhn4SoDWPerv5aTK
19FjuzAA1YDpne/DU+BwLjm3PTaC5EA/2krdh/U9XrptseqTrKvMbMq54xdzs9bW
atqmM802KyBsA1uGNUzARoRDvMziuQ9tF6BEjWph2mMIv6Dwj5+vLKBmPHWoMtOn
ZFEOY2ykN46KHexTYk99cQmv7VtCYnA5Uvr6NkmK2NyjcwUGlApUJ9OquNA+jQey
CMmYtln9KWU8fRzC95o8AQNRjB4V6ID9mCyAMacP04j8aKnoq6c8Fx4HSIw316QI
31Qi7OjlfqkAY9YFY/dTwirICdyUb2iRMcH1I13xF7PPV9FsG+EIthqcErxYHbpT
0ni9rBUtjTbwYOXT5oFmN5NeI3gyz7TY/YnfOo6/sySmuHt5x2Bc2HStrsXE9MV/
94iHI8ZwxaPE271ehXDXj2YcXfjcXUyC5i0FL/0Ipc6T/ibHx3E2E3HiFgJHJ/h5
oMtMQPE4fw2dbaInYdlxlTJO6fGDGDZ2lshZ9XvvkUJ4yNPzTW48+1AuYi7Kf/Y5
RPmQX4CRSFErZJQNwU/KYvuLI2QsJows/CakBzIg06EbF2z/Lv/nipjqjCVj9nSO
S6bzd5FFeQsY5DLFUzh0
=oLrF
-----END PGP SIGNATURE-----