Free AAAA (IPv6) Record Lookup & Checker

Your IP:
Check the DNS record Propagation in Multi-Region Check Multi-Region
Domain Type Primary NS Responsible Person Serial Refresh Retry Expire Minimum TTL
Name Server IP Address TTL
Domain Type TTL Record Value
Trace Result
Domain Type Record Status
Domain Type Record Status

Check live AAAA DNS records, TTL values, and trace the full root-to-authoritative resolution path.

AAAA (IPv6 Address) Records Overview

What is an AAAA record?

An AAAA record maps a domain name to its corresponding IPv6 address, supporting the newer IPv6 protocol.

Why do you need an AAAA record?

With the adoption of IPv6, an AAAA record ensures your website is accessible to users using IPv6 addresses.

AAAA record structure

An AAAA record includes the domain name, TTL, record type (AAAA), and the IPv6 address. Example: example.com. 3600 IN AAAA 2001:0db8:85a3:0000:0000:8a2e:0370:7334

How to create an AAAA record?

Add an AAAA record in your DNS host's dashboard: set the host (@ or a subdomain), paste the server's full IPv6 address as the value, and pick a TTL. Only publish an AAAA when the target actually answers over IPv6, and keep it alongside the matching A record so IPv4-only clients still resolve.

FAQs

Yes, a domain can have both to support both IPv4 and IPv6.

No, but having an AAAA record ensures compatibility with IPv6, which is becoming more widely used.

You can use online tools to check DNS records or use command-line tools like dig or nslookup.

An A record points a domain to an IPv4 address, while an AAAA record points it to an IPv6 address. Many domains publish both so they work over either protocol.

No. IPv4-only clients keep using your A record, while IPv6-capable clients can use the AAAA record. Both can coexist safely.

AAAA Record Troubleshooting & Common Fixes

Website feels slow or times out for mobile and broadband users

Modern operating systems and mobile carriers prioritize IPv6 via an algorithm called “Happy Eyeballs” (RFC 8305). If you publish an AAAA record but your web server software (Apache, Nginx, or Docker) is only listening on IPv4, browsers will attempt to connect via IPv6, hang for several seconds until the connection times out, and only then fall back to IPv4.

How to fix: Check your web server configuration to confirm it binds to both IPv4 and IPv6. In Nginx, ensure you have listen [::]:80; and listen [::]:443 ssl; in your server blocks. In Apache, verify Listen [::]:80 is active. If your server does not have a working IPv6 network interface, remove the AAAA record until IPv6 routing is fully configured.

Let's Encrypt / Certbot SSL validation fails after adding AAAA record

Automated ACME certificate authorities like Let's Encrypt always validate domain ownership over IPv6 if an AAAA record exists on the domain. If the IPv6 path is blocked by a firewall or routed incorrectly, certificate renewal will fail with an HTTP-01 challenge error.

How to fix: Check your hosting firewall (e.g. AWS Security Group, UFW, or cloud firewall) to ensure inbound traffic on port 80 and 443 is open for IPv6 (::/0), not just IPv4 (0.0.0.0/0). Test IPv6 connectivity directly with curl -6 -I https://example.com.

DNS manager rejects IPv6 address as invalid format

IPv6 addresses consist of eight 16-bit blocks separated by colons. Common errors include using the double colon (::) abbreviation more than once in an address, or entering an address with an attached CIDR prefix (such as /64).

How to fix: Double colon (::) represents consecutive zeros and can only appear once in an address. Remove any trailing subnet mask (e.g. /64) because DNS AAAA records require a single host IP, not a subnet block.

DNS Info extension for Chrome is now available

Install