Hi,
I've been looking into how I can let NSD pick up changes in it's config
file (zone additions, changes and removals).
Unless I am mistaken somewhere, NSD will only pick this up after a full
restart, which can take up to several seconds on my system with, so far,
a very small amount of zones (<10).
I would like to change the zone configuration of NSD up to every minute,
so I'm a bit worried about the outage window of an NSD restart
(potentially) every minute. Especially if the amount of zones would
become higher.
As far as I've been able to measure my actual window of unresponsiveness
is quite short, but I'm having doubts about my measurement method.
My questions:
(a) Is there a better way to change zone configuration
while NSD is running?
(b) Am I right in assuming that, if I have a large number of zones,
the restarts will start taking proportionally longer?
(c) Is there anyone that has tried to do something similar before,
and found a way to avoid this problem?
cheers,
Erik Romijn
On Wed, 22 Apr 2009, Erik Romijn wrote:> I've been looking into how I can let NSD pick up changes in it's config > file (zone additions, changes and removals). > > Unless I am mistaken somewhere, NSD will only pick this up after a full > restart, which can take up to several seconds on my system with, so far, > a very small amount of zones (<10).It picks up zone changed when you tell it to reload. Reload just will not pick up removed or added zones.> I would like to change the zone configuration of NSD up to every minute,What is the use case for this? :)> My questions: > (a) Is there a better way to change zone configuration > while NSD is running?Not that I know.> (b) Am I right in assuming that, if I have a large number of zones, > the restarts will start taking proportionally longer?Yes. But you might speed things up by running the zone compiler manually yourself so that your waiting time does not include zone compilations.> (c) Is there anyone that has tried to do something similar before, > and found a way to avoid this problem?I'd be interested in seeing why you need to add/remove zones every minute... Paul
Hi, We are also concerned about the length of the service break when adding new zones to the configuration file. When a new slave zone/new slave zones is/are added to the configuration file and the NSD is restarted, how long should it take until NSD continues to serve the previously added zones that already exist in the database? That is, is NSD able to continue to serve the previously added zones even if the zone transfers for the new zones have not been completed? In our case, the total amount of zones is a couple of thousands, which is why we'd like to avoid unnecessary restarts and service breaks of NSD. To be able to reload the NSD configuration file without restarting NSD would be a very nice feature for us, too. I know this topic has been discussed quite a lot... Antti