> 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. > > AskUpstream 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
> Em 30/11/2014, ?(s) 16:29:000, Rubens Kuhl <rubensk at nic.br> escreveu: > > >> 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.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. Rubens
Wouter Wijngaards
2014-Dec-01 19:18 UTC
[nsd-users] Downstream plus upstream zone transfer
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi Rubens On 12/01/2014 03:50 PM, Rubens Kuhl wrote:> >> Em 30/11/2014, ?(s) 16:29:000, Rubens Kuhl <rubensk at nic.br> >> escreveu: >> >> >>> 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. > > > 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. 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. Best regards, Wouter -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQIcBAEBAgAGBQJUfL8AAAoJEJ9vHC1+BF+NR8wP/0TFLBc+lQc/mvO3IUlQpWqn 6bmnC7QmzFQC1DgFWS7JAe/58FlVZNo0F9bI7o5OYIa87aIr5wfZa8ycE+6D/1eD BhN1WALgv2qcx7yMLEJ0qXIQ4trRad7Dl2XKeFWwdvrVwQz5ktNiWGEbjNevAwWf EXugK5yYl/oWSLaN3kqzWusY5Z2s3GLQpusD086ZsnutegIotm0S+Qb6zt6IUsy/ w5KeNMHv0fEpYzrY0J4+CywDfhy3HhD8DcnEYGEzQpAjqIb83e5mfh0SdkP132L5 zTmMBWPumdS4FQ5Vxymk4gJr5r5yxbx8lMMOcaCl/H6irHtGB6vhyBjkGczqoAJh u34uSbUXHp9M0DYIsfs+H9rIe2MdGmVNCLMJN+otPg+NWiMoh32C7FtchhCpV1Zb r7ux36ndtTJQ9iaJD3Uf7LVYAh2UQ1h/R5t5LN54Cvkg6YO2ccnEoaaYTWPy86vi 76Dd3Pt2hAgTSchcLyoH5GH+wxAIgv3NTqcjd7IjDb4Fp4d3mYR/XpMSpEFuxz1h anY6xqhjarISiQKEMK1i8YTDuJD0XgXG/0Buc8YkixZigXnZdYI6p3L6X3yuyBGw XnZJjYCAlBrEqWxgyC95pBL9BpaZ98hASHgLArMoTP3FApC06jYp0s+Ybuo2/Gxh zh6kcPwBLZT/vMgFNO8w =sJBg -----END PGP SIGNATURE-----