[nsd-users] nsd as master + slave

A. Schulze sca at andreasschulze.de
Fri Oct 10 14:05:29 UTC 2014

W.C.A. Wijngaards:

> So, increment (+1) the serial number of the SOA in the zonefile on
> disk.  At the master perform nsd-control reload.  That will read in
> the zonefile, and start sending notifies, and the slave then fetches
> the zone.  The manual transfer and notify commands are for control in
> case of operational difficulties, just a reload on the master of the
> zone should work.

I will retry this step by step...

> (the connection resets are because you shortened the SOA timer values
> significantly and the slave is indeed attempting to fetch the zone,
> but aborts the zone transfer as soon as it figures out you did not
> change the SOA serial number).

that clarify the errors.

But wouldn't it be better to log a warning at the slave?
Optional (configuration?) the slave could continue to fetch the zone
to avoid such errors at the server. Optional, that really depend on  
the zone size.

Anyway: the errors are really confusing and should not occur if a nsd  
talks to a nsd.


More information about the nsd-users mailing list