nsd users - Mar 2009 - NSD usage

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

Hi list,

after converting the djbdns-zonefile to
something NSD can read, I wonder about
the updating process. Currently I'm
doing something like this:

- - creating the zone: statements on the
  master and the slave in nsd.conf
- - create the zonefile referenced in the
  nsd.conf zone: statement on the master
- - do a nsdc rebuild && nsdc restart && nsdc notify

The slave has as per recommendation a
'nsdc patch' in it's crontab.

Is there a different way or does it need
to be done like that?

Also, I intentionally fubared the nsd.db
file, to see how it can be fixed. How do
I restore that file if it's gone/screwed?

Thanks and best regards,

Mit freundlichen Gruessen,

i. A. Sven Juergensen

- --
Fachbereich
Netze und Rechenzentren

KielNET GmbH
Gesellschaft fuer Kommunikation
Preusserstr. 1-9, 24105 Kiel

Telefon : 0431 2219-053
Mobil   : 0170 403 5600
Telefax : 0431 2219-005
E-Mail  : s.juergensen at kielnet.de
Internet: http://www.kielnet.de

Geschaeftsfuehrer Eberhard Schmidt
HRB 4499 (Amtsgericht Kiel)

PGP details at
http://pgp.kielnet.de/sjuergensen/

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.9 (GNU/Linux)

iEYEARECAAYFAkmv6RcACgkQnEU7erAt4TJANwCdH0a5KNyKTMT06J6Yj7p57KRJ
u/0AoM5nEeLHVYop4XcyGxiT9NwQ6Hgc
=PYFT
-----END PGP SIGNATURE-----

On Thu, 5 Mar 2009, Sven Juergensen (KielNET) wrote:
>  nsd.conf zone: statement on the master
> - - do a nsdc rebuild && nsdc restart && nsdc notify
nsd-3 should no longer requires seperate nsdc notify commands.
nsd-2 requires tehse.
> Also, I intentionally fubared the nsd.db
> file, to see how it can be fixed. How do
> I restore that file if it's gone/screwed?
Handling of a broken/missing nsd.db file could probably improve :)

Paul

Sven Juergensen (KielNET) wrote:
> The slave has as per recommendation a
> 'nsdc patch' in it's crontab.
> 
> Is there a different way or does it need
> to be done like that?
NSD keeps a journal in ixfr.db. If you don't run nsdc patch once in a
while, it may grow 'indefinitely' large.
> Also, I intentionally fubared the nsd.db
> file, to see how it can be fixed. How do
> I restore that file if it's gone/screwed?
Run nsdc rebuild again. You can use the nsd-xfer program to transfer the
zones you are secondary for.

Regards,

Matthijs

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 544 bytes
Desc: OpenPGP digital signature
URL:
<http://lists.nlnetlabs.nl/pipermail/nsd-users/attachments/20090306/93651a78/attachment.bin>