[nsd-users] RFC glitch regarding IXFR

[Matthijs Mekking]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi Rick,

On 04/16/2012 09:37 AM, Rick van Rein wrote:
> 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


> This is not a serious incompatibility, but it could simplify the
> life of new adopters of NSD somewhat.
> 
> 
> Hopefully useful,
> 
> Rick van Rein OpenFortress 
> _______________________________________________ nsd-users mailing
> list nsd-users at NLnetLabs.nl 
> http://open.nlnetlabs.nl/mailman/listinfo/nsd-users

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQEcBAEBAgAGBQJPi9OWAAoJEA8yVCPsQCW5ljAIAMJZq8dwdgCEFbEkTjqYtxYz
hh/n/LsalYXhCQiaS+LYo2vb5MLMGezp6DRkmfny6kV309xCZPvHJrE/s0J47Crc
y1LBIdyv0ASnr+RjtOjlWb1VvU6y868QhY2zPjxrNFNj95QKsKUso+HhaJ4OlIKC
ENyxpI362gqlyzwB+rixV/uJ9vVPx7qeJr3ZUf4tY+NplSJqg5FYOfbZh3ZrdWWD
8bBOh03Qtkbq6h3aTD9lN8Lb8ZDtgkHKGCQO6wVoUsJS0ouGTpytyHdsHzH2C0Lu
16nvAG4wyw93tjzi4axjr+c6KaUo/fQB9nz7jUg+0+cXfvaXdon914VhdMMViEI=
=lOfV
-----END PGP SIGNATURE-----