I've been comparing responses from BIND, Knot and NSD, and looking at
response sizes.
Knot version 2.3 and above, and BIND with "minimal-responses yes",
return minimal responses. They only add data to the authority and
additional sections if necessary. For example, a query for ./IN/SOA to
BIND (with "minimal-responses yes") or Knot returns a 389-byte response:
This is because NSD has added data to the authority and additional
sections (which I have not shown).
If NSD had the ability to minimise responses the way BIND and Knot do,
would anyone want or use it? Do any folks feel like NSD should have this
feature, or do you folk think that NSD's responses are just fine the way
they are, and you don't care about sending out more bytes?
If NSD had the ability to minimise responses the way BIND and Knot do,
would anyone want or use it?
Hello Anand,
Although I use to compile NSD with minimal responses enabled
(explicit without --disable-minimal-responses)
I also noticed the answers are larger compared to BIND servers.
Although I use to compile NSD with minimal responses enabled
(explicit without --disable-minimal-responses)
I also noticed the answers are larger compared to BIND servers.
Yes, I would use it...
Thanks for your reply. I've submitted this enhancement request to the
NSD developers:
Wouter has already solved this, and provided a new option called
"minimal-responses" for nsd.conf. It defaults to "no". Setting it to
"yes" makes NSD emit small responses, with the exception of NS queries.
Thanks Wouter!