nsd users - Nov 2014 - Downstream plus upstream zone transfer

Hi there. 

When NSD is in a role of being both slave for a zone and providing XFR services
for that zone, what would be the expected behaviour when while doing an AXFR, it
gets notified or get a new AXFR/IXFR from upstream ? Would it be terminating the
in-progress transfer abruptly or still going thru until the transfer ends ?

Tks,
Rubens

It sounds like you have a problem or concern that you didn't describe.

If you have frequent transfers of large zones (maybe to slow slaves or from a
slow master?) you'll be better off having the intermediary "transfer
hub" run something that can serve IXFR transfers. Bind works well for this,
even if the upstream can't do IXFRs.

Then the downstream hosts will just get a small update to apply.

Ask

-- 
http://askask.com/

> On Nov 30, 2014, at 3:51 PM, Ask Bj?rn Hansen <ask at develooper.com>
wrote:
> 
> 
> It sounds like you have a problem or concern that you didn't describe.
Indeed, but I'm trying not to categorise something as a problem before
knowing what the expected outcome was.
> If you have frequent transfers of large zones (maybe to slow slaves or from
a slow master?) you'll be better off having the intermediary "transfer
hub" run something that can serve IXFR transfers. Bind works well for this,
even if the upstream can't do IXFRs.
> Then the downstream hosts will just get a small update to apply.
> 
> Ask
Upstream can do IXFR, and the fetch process from upstream uses IXFR for 99.9% of
times (AXFR is forced every few days).
Downstream slave is the one forcing AXFR. 


Rubens