Why You're Seeing So Many AAAA Queries—Even If You Don't Use IPv6
Understanding Dual-Stack Behavior, DNS Query Patterns, and the Rise of AAAA Records
As more networks and devices adopt IPv6, DNS query patterns are evolving—and many UltraDNS users have started noticing an uptick in AAAA (IPv6) queries, even when their domains don’t serve IPv6 traffic.
If you've reviewed your DNS logs and wondered, "Why am I getting so many AAAA queries when I haven't even configured IPv6?"—you’re not alone. In this post, we’ll break down the technical reasons behind this behavior and explain why it’s expected in today’s internet ecosystem.
What Are AAAA Records?
DNS AAAA records are used to map domain names to IPv6 addresses, much like A records map domains to IPv4 addresses. As the internet transitions toward IPv6 to support a growing number of devices, operating systems, browsers, and applications are increasingly designed to look for both types of records by default.
Why Clients Send AAAA Queries by Default
Here are the core reasons you’re seeing AAAA queries, even when no AAAA record exists for your domain:
1. Modern Operating Systems Use Dual-Stack by Default
Most contemporary operating systems—including Windows, macOS, iOS, Android, and major Linux distributions—enable both IPv4 and IPv6 networking out of the box. In a dual-stack configuration, DNS resolver libraries typically request both A and AAAA records for a domain as part of their resolution process.
So even if the client is ultimately going to use IPv4, it will still ask for an AAAA record just in case an IPv6 path is available.
2. The "Happy Eyeballs" Algorithm (RFC 6555)
To improve connection times and user experience, web browsers and other network-aware applications implement the Happy Eyeballs algorithm. This mechanism simultaneously attempts connections over both IPv4 and IPv6 and chooses the one that responds first.
In order to do this, the client must first obtain both A and AAAA records. This often results in simultaneous or closely sequenced DNS queries for both record types—regardless of whether your infrastructure supports IPv6.
3. Client-Side Resolver Behavior
DNS resolution libraries built into operating systems are optimized for speed and compatibility. When a DNS lookup is initiated, the resolver will typically issue both A and AAAA queries, even if only one of the protocols is used or available. This behavior is standardized across platforms and does not indicate any kind of misconfiguration.
4. IPv6 Preference in Some Networks
Certain networks—especially those operated by ISPs, mobile carriers, universities, and enterprise environments—prioritize IPv6 over IPv4. Applications running in those environments will attempt to use IPv6 first, and so naturally query for AAAA records.
In these scenarios, clients may attempt to use IPv6 for performance, policy compliance, or network efficiency reasons.
5. DNS Pre-Fetching by Browsers and CDNs
Browsers like Chrome and Firefox often pre-fetch DNS records to speed up browsing experiences. This means DNS queries (both A and AAAA) may be issued before the user even clicks on a link. Content delivery networks (CDNs) and recursive resolvers may also issue parallel queries in anticipation of future requests, amplifying the number of AAAA queries you see in your logs.
6. Fallback Mechanisms and Retry Logic
Sometimes applications issue AAAA queries as a fallback—if the A record query times out or takes too long, the client may try an AAAA query in parallel. This retry logic is built into many modern networking libraries and is part of fault-tolerant design best practices.
What Happens If No AAAA Record Exists?
If your domain does not have an AAAA record, your authoritative DNS server (like UltraDNS) will return a NOERROR response with an empty answer section. This tells the client that the domain is valid, but there’s no AAAA record available. The client will then typically proceed to use the A record (IPv4) response, if available.
This is completely normal behavior and is not an error.
Should You Be Concerned?
Not at all. The presence of AAAA queries in your DNS logs is expected behavior on today’s modern internet. It does not indicate an issue with your configuration. However, this pattern can be useful if you're evaluating whether to start supporting IPv6—you may already have demand for it from clients.
If you're considering IPv6 adoption or monitoring dual-stack readiness, the volume of AAAA queries can serve as an early indicator of how much IPv6 traffic your domains might support in the future.
Final Thoughts
Seeing AAAA queries in your UltraDNS reports—even when you don’t support IPv6—isn't just normal, it’s a sign of the internet moving forward.
Understanding the “why” behind these patterns can help you better interpret DNS traffic, optimize configurations, and plan for future IPv6 support if needed. As always, UltraDNS provides visibility and control at every step, whether you're fully IPv4, dual-stack, or preparing for what’s next.
Want to dive deeper into your query data? Try using UltraDNS Private Data Lake to analyze IPv6 vs. IPv4 trends over time.
Would love to hear your thoughts or questions—drop them in the comments below!