nsd reload issue
mark at NLnetLabs.nl
Fri Jun 29 13:30:54 CEST 2007
-----BEGIN PGP SIGNED MESSAGE-----
Måns Nilsson wrote:
> --On torsdag, torsdag 28 jun 2007 17.58.31 -0500 Kevin Wormington
> <kworm at sofnet.com> wrote:
>> I'm using NSD 3.0.5 and I have noticed that after I add a new zone to
>> the config file and do an "nsdc rebuild" it will compile the database
>> just fine. When I do an "nsdc reload" it get a message in syslog about
>> the database being corrupt and it keeping the in-memory copy. If I do
>> an "nsdc stop; nsdc start" it loads the new database just fine.
>> Any ideas?
> I have the same problem. Most irritating. I think it can be summarised to
> "NSD does not seem to like getting new zones without start/stop". I have
> been looking through the documents for a procedure that I simply
> overlooked. It does not look like that. Please tell me I'm wrong!
I'm sorry to tell you that you are not wrong ;-)
The way NSD is currently implemented, it is indeed the case that you
need a restart to re-read the config (and thus get aware of new zones).
The rationale behind this is (was?) that many configuration settings
simply can't be done without a restart (think of dropped privileges, etc.).
However, we do recognize the need for users to be able to add zones
without a restart. Code-wise this is not trivial, but it is certainly
something that we would like to implement. It's too early to come up
with an ETA at this moment, but we will keep the list updated on the status.
Hopefully this clears up the issue.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
-----END PGP SIGNATURE-----
More information about the nsd-users