Hello,
NSD cannot serve IXFR, and to avoid asking for it if it runs
on another node, it requires explicit configuration on that other
node that AXFR should be used and not IXFR.
RFC 1995 on IXFR states something that makes the above incompatible:
"If incremental zone transfer is not available, the entire zone is
returned." -- section 4, on "Response Format".
This is not a serious incompatibility, but it could simplify the life
of new adopters of NSD somewhat.
Hopefully useful,
Rick van Rein
OpenFortress
Hi Rick,
Hello,
NSD cannot serve IXFR, and to avoid asking for it if it runs on
another node, it requires explicit configuration on that other node
that AXFR should be used and not IXFR.
NSD will (by default) fallback to AXFR for backwards compatibility, so
it is not required to set AXFR, but if you know the server is NSD, it
is useful to set it.
RFC 1995 on IXFR states something that makes the above
incompatible: "If incremental zone transfer is not available, the
entire zone is returned." -- section 4, on "Response Format".
NSD is a bit specific on that matter. It is true that the IXFR client
features have been implemented, but not the IXFR server features.
Therefore, I think NSD should return NOTIMPL: You will let the
requestor know that it will never get an IXFR back.
The text in RFC 1995 is true if IXFR is implemented, and specifically
the server features.
Best regards,
Matthijs
Hello,
The text in RFC 1995 is true if IXFR is implemented, and specifically
the server features.
Good point. Given this, I agree that it doesn't apply here.
And "you will never get IXFR" is definately useful information.
-Rick