Hi Charles,

this is hard to say without a specific example, but generally the Knot DNS is trying to send minimal usable response that doesn't include resource records that won't be used by modern resolvers.

The modern resolvers generally throw away any records that are not within very strict bailiwick (e.g. anything extra that resolver hasn't asked for will be discarded). If you can give us an example of such responses we can decode why the records won't be used by resolvers (or whether it is really bug in Knot DNS).

Cheers,
Ondřej

On June 15, 2015 10:12:14 PM GMT+02:00, Charles Musser <cmusser@sonic.net> wrote:
Hi,

We've been running Knot 1.6.3 as a slave server and it's been working well. However, I notice that a "dig" against this slave for a domain does not return an "ADDITIONAL" section, but the same query against another slave that runs BIND does return one. I couldn't find any Knot configuration directive that would control this. Is there something I missed or additional configuration needed elsewhere to make the ADDITIONAL info available?

Thanks,

Chuck

knot-dns-users mailing list
knot-dns-users@lists.nic.cz
https://lists.nic.cz/cgi-bin/mailman/listinfo/knot-dns-users

--
Sent from my Android device with K-9 Mail. Please excuse my brevity.