AAAA Record Lookup Tool

Check AAAA records instantly across multiple public DNS resolvers to validate IPv6 routing.

How to troubleshoot IPv6 routing with an AAAA Lookup

As the internet transitions to dual-stack networking, verifying your IPv6 configuration is crucial. Enter your domain name above to instantly query its AAAA record. Our tool checks multiple public DNS resolvers globally to help you confirm IPv6 connectivity and spot propagation delays.

Interpreting your lookup results

  • NXDOMAIN vs No Answer: If you see NXDOMAIN, the domain itself doesn't exist. If the domain exists but returns no AAAA record, it simply means IPv6 is not configured. Modern browsers will seamlessly fall back to the A record (IPv4).
  • Inconsistent IPv6 Addresses: If Google DNS shows your new IPv6 address but Cloudflare still shows the old one, you are actively experiencing DNS propagation. Wait for your TTL to expire.
  • CDN and Firewall IPs: If you are using a reverse proxy or CDN like Cloudflare, the AAAA lookup will return their IPv6 edge servers. Ensure your origin server is also properly configured to accept IPv6 connections from the CDN.
  • Broken IPv6 Routing: If an AAAA record is present but the server is unreachable via IPv6, users might experience slow load times (until "Happy Eyeballs" fallback kicks in). Always ensure your firewall rules allow IPv6 traffic.

AAAA record lookup for IPv6 readiness

An AAAA record maps a hostname to an IPv6 address. It enables dual stack sites to serve users on IPv6 and can improve reachability in networks where IPv4 is limited. Many browsers use Happy Eyeballs, which means they try IPv6 and IPv4 in parallel and pick the fastest. If your IPv6 path is broken, users can still experience delays, so verifying AAAA records and actual connectivity is important.

Common AAAA issues include publishing an IPv6 address that does not route, forgetting to open IPv6 firewall rules, or pointing to a server that only listens on IPv4. Another pitfall is mixing AAAA for the apex while www stays IPv4 only. This lookup shows AAAA results across resolvers so you can validate what the public DNS actually returns and spot inconsistent propagation.

If you need related checks, try Check A record online and Check DNS propagation check online.

Only if the service is reachable over IPv6. Publishing AAAA without working IPv6 can lead to slow or failed connections. Start with critical hostnames, confirm connectivity, then expand.

This is a propagation or caching issue. Resolvers may cache older records based on TTL. Check authoritative records and wait for caches to expire.

No. AAAA complements A. Many sites run both so clients can choose. Removing A records will break IPv4-only networks.

Happy Eyeballs is a client strategy that tries IPv6 and IPv4 nearly simultaneously. If IPv6 is misconfigured, it can still cause connection delays. A clean AAAA setup helps avoid these issues.

IPv6 addressing and routing can differ between providers and regions. Verify the exact address assigned to your host and make sure the AAAA record matches the live interface.

Yes. Use a low TTL during migrations to speed up changes. After stability, increase TTL for cache efficiency.

A record lookup CNAME lookup DNS propagation check

Related tools

Check A record online Check CNAME record online Check NS record online Check DNS propagation check online