-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi Anand,
On 06/28/2015 01:38 PM, Anand Buddhdev wrote:> My colleague Robert and I have just discovered something
> interesting about NSD's responses.
>
> For a query of the form:
>
> dig @rootserver com ns +norec +bufsize=512 +nsid
>
> NSD does not return the NSID in the response. It fills up the
> entire additional section with as many address records as
> possible.
>
> In contrast, BIND and Knot omit some of the addresses in order to
> accommodate the NSID.
It was a bug in the nsid code, it has been fixed in the code repo (and
I've backported that to NSD3).
Best regards,
Wouter
>
> I personally prefer the BIND/Knot behaviour. Usually, NSID will be
> requested by a debugging or measurement type query, where one
> doesn't care too much about some missing address records. If NSID
> is requested, then the name server should try to accommodate it,
> while forgoing some of the address records.
>
> If it's not too much work, could I request that NSD be modified to
> work like this?
>
> Regards, Anand _______________________________________________
> nsd-users mailing list nsd-users at NLnetLabs.nl
> http://open.nlnetlabs.nl/mailman/listinfo/nsd-users
>
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
iQIcBAEBAgAGBQJVlRn/AAoJEJ9vHC1+BF+NoyAP/RV9SjiIHTdbjb6zDATJYzGU
uwrYqz5wxJR2Jwu0YA9o6AZIKlBiJ3IalwdZQ/UOW/zS0tSPtpk6xcLv7eMXBV9r
jqcVxGlWQs8GJSWL6RkxaEzXLZJpa4uLHNRPPu+KE3HLKQaom8trxRbv05DXyDja
EJCmMxE/l0eNBOBTEdvmsqMXtMfNaBFUVDAzguW/YGmfSsAVJ1+nR422B2YzzPwn
f6e1yH0pn92DrbqNY2VrcMDxqBT6vI0FswumnJaFcle75GFBW576G6ymNANsXrad
7UNSbv6DjUZ64ziZtRlgpw7jbANMxyWH4oc+ePQ66UGJ/pB7rXmA342gyaieOlQ2
nWqFyZmNORK5CI9s2g0Gn7czWKhHpAHDOVGjDrhdO7dlJUgXBbu3PhP0RM36B6dJ
3xXYHTaG/EIdcldrMDhai2A9GagbaiywGNXj5JKpi2MMvyDsQoaaGZLXjgtg/F37
UqbKmahQ/SgBspxYHHGzKnwCtaY7alNhW8p33PRVU6hHRoQUkHkAZSCpEg5L9SvV
pjDATblJ3S+WGO8RNrYZD45IroilOsi4TXWxWBkZVfOoeFwnoPCv6W1IhoyjBO/a
w2l/o+39lMXzPzJPAcQejgpru6w1ns0kG9TQHW6dB4637ettsL+O1Hih+pheLHuQ
tqAYjM8txeuS76GucPaT
=K5YN
-----END PGP SIGNATURE-----