-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi Paul,
Previously, NSD always made his IXFR requests over UDP.
Since 3.2.0, we default to IXFR/TCP.
The UDP option is too still make IXFR/UDP requests.
We strongly recommend to use TSIG if you use IXFR/UDP.
NSD will still try to AXFR the zone with TCP, if the zone's current
serial is 0, or if the master server does not implement IXFR.
Best regards,
Matthijs
Paul Hoffman wrote:> In my nsd.conf file, I have:
>
> zone:
> name: dimeadozen.org
> zonefile: slave/dimeadozen.org
> allow-notify: 85.214.50.249 NOKEY
> request-xfr: UDP 85.214.50.249 NOKEY
>
> Yet in the log, I see:
>
> [1259891852] nsd[6570]: error: Could not tcp connect to 85.214.50.249:
Operation timed out
>
> I see the same thing if I remove the "UDP", but my real question
is: why is NSD trying over TCP if I specified UDP?
>
> --Paul Hoffman
> _______________________________________________
> nsd-users mailing list
> nsd-users at NLnetLabs.nl
> http://open.nlnetlabs.nl/mailman/listinfo/nsd-users
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iQEcBAEBAgAGBQJLGMESAAoJEA8yVCPsQCW5A2YH/jXTdSlonuL4e3CioZZfTTTL
L7uYcHffIJjtq4QYoiGiio8ahuuAhSgkL8pHwdnkfqhwYH/aGBYfoYE91RNhLjyI
AfuvFQ/58Y1tfGVi0tApWO6IqmoNnQkrVCYFUURxG4yH6WPMQHdNrhZQpd+aqN11
9CnSgJ2skUridmaKm1Wm/IjNCspfLav/NUjQ4+NFCLL3AhMFvz66/McScPXeZofs
hnhFq08J4dxGKKmEQaaA6yhfwUpNu+x3ztS8dZtv1Ci0yXq7kRdUz8SqLCO2vzcS
tJPemAf6R8n8CVPu5h7X5fBwVVvyfRF6Tkx7vSUZCBLSZ9RV3opAGjcltN0V99Q=L8KE
-----END PGP SIGNATURE-----