[nsd-users] Downstream plus upstream zone transfer

Rubens Kuhl rubensk at nic.br
Mon Dec 1 19:25:01 UTC 2014

>> BTW, it would be interesting to know whether this has changed in
>> newer NSD 3.2 or 4.x builds, or if there is still a design decision
>> to interrupt downstream AXFR if there is notification of a zone
>> update.
> There is no transfer interruption.  The transfer should conclude, the
> notify is simply recorded for future actions once the current actions
> are done.

At least with 3.2.17, transfer interruption is exactly what's happening. 

> If the downstream transfer is very slow, it will get interrupted as
> the new zone is hosted and the old-zone's process gets killed off.

The downstream transfer is taking somewhere between 13 and 59 seconds depending on network conditions, so it's slow but not incredibly slow. Sometimes it's happening while the zone gets updated, and then the TCP session is simply ended in the middle of the transfer. 


More information about the nsd-users mailing list