AAAA record: what it is and how to check it

Points a domain or subdomain to an IPv6 address, the successor of IPv4.

Check with the DNS Lookup

What it is

An AAAA record connects a name, such as example.com, to an IPv6 address, such as 2001:db8::10. It does exactly what an A record does, but for the newer version of the Internet Protocol.

IPv6 was created because the roughly four billion IPv4 addresses are not enough for every device on the internet. IPv6 addresses are 128 bits long, which gives an almost unlimited supply. The AAAA record type was defined in RFC 3596.

How it works

Resolution works the same way as for A records. A device asks its resolver for the AAAA record of a name; the resolver follows the delegation to the domain’s authoritative nameservers and returns the IPv6 addresses with their TTL.

Most operating systems ask for A and AAAA at the same time. If both exist and the device has IPv6 connectivity, it tries IPv6 first and falls back to IPv4 if the connection does not succeed quickly. This behaviour is called Happy Eyeballs (RFC 8305). Because of the fallback, a broken IPv6 setup often shows up as “the site is slow for some people” rather than “the site is down”.

The DNS query itself can travel over IPv4 or IPv6. Asking for an AAAA record over IPv4 is perfectly normal: the record type describes the data, not the transport.

Dual stack and IPv6-only

Most sites today are dual stack: they publish both A and AAAA records and serve the same content over both protocols. Some networks, especially mobile ones, give their users IPv6 only and reach IPv4-only sites through a translation service (NAT64 with DNS64, RFC 6147). In that setup, the network’s resolver creates a synthetic AAAA record from your A record. Publishing a real AAAA record avoids that translation step and gives those users a direct path to your server.

Syntax and fields

Field Example Meaning
Name www.example.com. The name being described.
TTL 3600 Cache lifetime in seconds.
Class IN Internet.
Type AAAA The record type.
Data 2001:db8::10 One IPv6 address.

IPv6 addresses are written as eight groups of four hexadecimal digits separated by colons. Two shortening rules apply (RFC 5952 defines the recommended form):

  • Leading zeros in a group can be dropped: 0db8 becomes db8.
  • One run of consecutive all-zero groups can be replaced by ::, once per address.

So 2001:0db8:0000:0000:0000:0000:0000:0010 and 2001:db8::10 are the same address. Our tools always display the short form.

Examples

A website reachable over both IPv4 and IPv6:

example.com.        3600  IN  A     192.0.2.10
example.com.        3600  IN  AAAA  2001:db8::10
www.example.com.    3600  IN  A     192.0.2.10
www.example.com.    3600  IN  AAAA  2001:db8::10

A mail server with an IPv6 address, referenced by an MX record:

example.com.        3600  IN  MX    10 mail.example.com.
mail.example.com.   3600  IN  A     198.51.100.25
mail.example.com.   3600  IN  AAAA  2001:db8:25::1

Two IPv6 addresses for the same name:

api.example.com.    300   IN  AAAA  2001:db8:1::a
api.example.com.    300   IN  AAAA  2001:db8:2::a

Common mistakes

  • Publishing an AAAA record for a server that does not listen on IPv6. The web server, firewall and hosting network must all accept IPv6 traffic. Test the address directly before publishing the record.
  • Forgetting the firewall. Firewall rules are often written for IPv4 only. An IPv6 address with no rules at all may be blocked entirely, or worse, left completely open.
  • Using a link-local or unique local address. Addresses starting with fe80: (link-local) or fc/fd (unique local) only work inside a local network and should never appear in public DNS.
  • Keeping an old AAAA after a migration. People often update the A record and forget the AAAA. IPv6 visitors then keep reaching the old server, which can be hard to notice if you test from an IPv4-only connection.
  • Typing errors in the address. Using :: twice in one address is invalid, and a group can have at most four hex digits. Most DNS panels reject these, but always double-check by looking the record up after saving.
  • Missing reverse DNS for mail. A mail server sending over IPv6 without a matching PTR record is likely to have messages rejected or marked as spam.

How to check it

Open the DNS lookup tool and choose type AAAA. You will see each IPv6 address, the TTL and the response status. An empty answer with status NOERROR means the name exists but has no IPv6 address.

To confirm a change has reached the public resolvers, use the DNS propagation checker with type AAAA. To see who operates an IPv6 address and whether it has reverse DNS, paste it into the IP lookup.

  • A: the IPv4 equivalent. Most sites publish both.
  • PTR: reverse DNS for IPv6 lives under ip6.arpa.
  • CNAME: an alias that inherits both the A and AAAA records of its target.
  • HTTPS / SVCB: can carry ipv6hint values for faster connections.

Frequently asked questions

Do I need an AAAA record?

Only if your server is actually reachable over IPv6. Many visitors, especially on mobile networks, have IPv6 connectivity, so publishing an AAAA record for a working IPv6 server is good practice. Publishing one for a server that does not answer on IPv6 causes slow or failed connections.

Why is it called AAAA?

An IPv6 address is 128 bits long, four times the 32 bits of an IPv4 address held in an A record. The name AAAA ('quad-A') reflects that.

What happens if a domain has both A and AAAA records?

Modern clients look up both and use an algorithm called Happy Eyeballs (RFC 8305): they try IPv6 first and fall back to IPv4 quickly if IPv6 does not connect. Both records should point to the same service.

Should I add a PTR record for my IPv6 address?

For mail servers, yes: many receivers check reverse DNS on IPv6 connections just as they do on IPv4. The PTR is set by whoever controls the address block, usually your hosting provider, under ip6.arpa.