AAAA record
What is AAAA record?
An AAAA record maps a hostname to an IPv6 address, the job an A record does for IPv4, defined in RFC 3596. A dual-stack domain publishes both, letting a resolver pick whichever address family the path supports. AdminKit's DNS lookup tool queries AAAA alongside A, MX, TXT, NS and CAA, so a missing AAAA record is easy to spot.
By AdminKit team, Netbase JSC · Updated
An AAAA record maps a hostname to an IPv6 address, the same job an A record does for IPv4, just for a 128-bit address instead of a 32-bit one. RFC 3596 defines the AAAA record type specifically for this purpose, as part of the broader set of DNS extensions written to support IPv6 alongside the IPv4-oriented record types RFC 1035 originally defined; it’s listed as type 28 in IANA’s DNS Parameters registry. A dual-stack domain typically publishes both an A and an AAAA record for the same hostname, letting a connecting client’s resolver choose whichever address family it and the network path actually support; a domain with only an A record is IPv4-only regardless of whether the server itself supports IPv6. AdminKit’s DNS lookup tool queries AAAA records alongside A, MX, TXT, NS and CAA for any domain, so a missing AAAA record is easy to spot when auditing a domain’s IPv6 readiness. How many clients can actually use that AAAA record is a separate question: Google publishes ongoing IPv6 adoption statistics showing the percentage of its users who reach it over IPv6, overall and per country. The plain IPv4 record it mirrors is covered separately in the A record entry. A client with both records available typically races a connection to each via Happy Eyeballs rather than waiting for one to fail before trying the other.
AAAA record is part of AdminKit’s DNS cluster; the full AdminKit glossary lists other related terms.
Frequently asked questions
Does a domain with an A record automatically have an AAAA record too?
No -- a domain with only an A record is IPv4-only regardless of whether the server itself supports IPv6. The AAAA record has to be published separately for the domain to be reachable over IPv6.
Why do dual-stack domains publish both A and AAAA records?
Publishing both lets a connecting client's resolver choose whichever address family it and the network path actually support, rather than forcing every visitor onto one protocol version.
How does a client choose between a domain's A and AAAA addresses?
A client with both records available typically races a connection to each via Happy Eyeballs, rather than waiting for one to fail before trying the other, so it ends up using whichever address family actually connects fastest.
Is a missing AAAA record something to check for?
Yes -- since IPv4 and IPv6 readiness are published as separate record types, a domain auditing its own IPv6 support has to specifically query for AAAA records rather than assume one exists because an A record does.