On Tue, Mar 22, 2016 at 7:41 AM, Tony Finch <d...@dotat.at> wrote: > Marek Vavruša <mvavr...@cloudflare.com> wrote: > > > > there was an interest in reducing latency for address record lookups. > > Me and Olafur wrote a draft on adding AAAA records to A answers and > > treating them as authoritative. This fixes latency issues with NS > > A/AAAA discovery in resolvers and improves caching for clients (AAAA > > already cached by the time client comes asking for it).
I think the reverse should also be done: add "A" answers to AAAA queries. Some possible reasons, although these might not be the best reasons: I thought that most dual-stack computers prefer IPv6 to connect, and thus I assumed that they would do an AAAA query first, in which case it would be good to return an "A" record if the AAAA query finds no answer, assuming that the client is likely to fall back to "A". There are probably also many clients where the stack thinks it might have IPv6 connectivity, but it really does not, so it will have to fall back to "A", even if an AAAA answer exists. I am almost certain someone will explain why I am wrong, but I at least wanted this discussed. -- Bob Harold
_______________________________________________ DNSOP mailing list DNSOP@ietf.org https://www.ietf.org/mailman/listinfo/dnsop
