AAAA Record Lookup
Check AAAA records (IPv6 addresses) for any domain across 12 global DNS resolvers. Free real-time DNS propagation checker.
What is an AAAA record?
An AAAA record ("quad-A") maps a hostname to an IPv6 address. It's the IPv6 equivalent of an A record. As IPv6 deployment grows, dual-stack hosts publish both A (IPv4) and AAAA (IPv6) records, and clients prefer IPv6 when both are available.
When to check AAAA records
- You're rolling out IPv6 and need to confirm the AAAA record is live worldwide
- A user on an IPv6-only network reports the site is unreachable
- You're auditing dual-stack readiness for a domain
- You're verifying that disabling IPv6 (removing the AAAA) actually propagated
Reading the results
An AAAA record value looks like a colon-separated IPv6 address (2606:2800:220:1:248:1893:25c8:1946). Multiple AAAA records are common for redundancy and load balancing. If a resolver returns no AAAA but does return an A record, the domain is IPv4-only: not a problem unless you specifically need IPv6.
Common errors and pitfalls
- "NODATA" instead of an answer: the domain exists but has no AAAA. Different from NXDOMAIN; the name is fine, just not v6-enabled.
- Site loads on IPv4 but not IPv6: verify the AAAA actually resolves to a working backend. A misconfigured AAAA pointing at a dead host causes IPv6 clients to time out before falling back.
- "Happy Eyeballs" hides bad AAAAs: a slow IPv6 path doesn't break the site for users (it falls back), but it adds latency. Worth verifying both stacks work cleanly.
FAQ
Why does a domain have both A and AAAA records?
That's a "dual-stack" deployment. The domain works on both IPv4 and IPv6 networks. Clients on dual-stack networks (most modern OSes) try IPv6 first via "Happy Eyeballs" and fall back to IPv4 if the IPv6 connection fails or is slow.
Will every resolver return AAAA records the same way?
Yes: AAAA is a standard record type. Differences between resolvers usually mean stale cache, not protocol issues.
Do I need AAAA records?
Not strictly. The internet still works without IPv6. But IPv6 traffic is now ~40% of Google's queries globally, and is mandatory in some networks (mobile carriers, parts of Asia). Dual-stack is the standard recommendation for any new deployment.
Can I publish AAAA without A?
Yes: IPv6-only deployments are technically valid. They cut off IPv4-only clients, which is a small but non-zero share of the internet, so it's mostly used for internal services or experimental setups.
Why is one of my AAAAs different across resolvers?
Same reasons as A records: stale cache or GeoDNS. AAAA-aware GeoDNS is increasingly common as IPv6 deployment grows.
Background reading
For the full DNS-record context, see the DNS Records Explained guide.