dig -t A www.youtube.com @8.8.8.8 This is not the equivalent of what is happening here. First, the resolver in dig is not affected by this issue, it is much more robust than the resolver in the various libc implementations. This issue is really best viewed with a packet capture. Second, you are not...

I think that in this case having a A records sent in the Answer section of a response to an AAAA query would also lead to undesired behaviour, though I have not tested it specifically.

I don't think I would go that far without knowing the codebase. Integrating third-party developed services in a robust way requires a lot of work and tends to have a large amount of hidden fiddling. I would hope that there would be a test suite of clients to ensure compatibility for a service like D...

Something's not kosher with the way CNAME DNS results are handled in this version. I noticed the same . The 7.6rc1 behaviour of putting extra A response records in responses for AAAA queries for CNAMEs confuses some common DNS client implementations. Windows and dig are not affected, but glibc and ...

Hi all, I don't have permission to reply to the announcement thread, so I'm posting here. The DNS server in 7.6rc1 serves cached CNAME responses in a way that causes getaddrinfo(3) to error out in at least recent versions of glibc. This causes most Linux and many IoT applications to break when tryin...