[nsd-users] nsdc reload & changes to the zone list
matthijs at NLnetLabs.nl
Tue Jul 22 10:35:43 CEST 2008
-----BEGIN PGP SIGNED MESSAGE-----
In the latest 3.1.1 release, the message is changed to:
"cannot load database. Zone foo.com in db nsd.db, but not in config file
(might happen if you edited the config file). Please rebuild database
and start again."
Imo, a less confusing message than the corrupted database message.
- - Matthijs
Joerg Sonnenberger wrote:
> Hi all,
> I got asked by a nsd user a while ago over the following behavior:
> (1) A zone was added or removed in nsd.conf
> (2) nsdc rebuild was run
> (3) nsdc reload was executed
> Now in syslog the following message can be found:
> corrupted database/bad config, zone example.com.
> in db /var/db/nsd.db, but not in config file. Cannot load database.
> Please rebuild database and start again.
> PR 193 concluded that the requirement to do a restart is ok, it was open
> whether the message should be changed.
> I think something like
> corrupted database /var/db/nsd.db or modified zone configuration.
> Please rebuild the database or restart the daemon.
> is more likely to guide the user to the problem. What do you think?
> nsd-users mailing list
> nsd-users at NLnetLabs.nl
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
-----END PGP SIGNATURE-----
More information about the nsd-users