comparison Domains & DNS
DNS A and AAAA records
Compare DNS A and AAAA records by address family, check both sets independently and avoid assuming IPv6 always works.
What it means
An A record associates a DNS name with an IPv4 address. An AAAA record associates a DNS name with an IPv6 address. They are separate DNS record types: one hostname can publish A records, AAAA records, both or neither. DNS provides candidate addresses; reachability, network selection and the web server's listening configuration determine whether a connection succeeds. A record AAAA record
Try it
Example — inspect both address families. These addresses are reserved documentation examples and are not real endpoints. The sample represents DNS data, not an active query.
www.example.com. 300 IN A 192.0.2.25
www.example.com. 300 IN AAAA 2001:db8::25The TTL displayed here is 300 seconds for each record in this simple illustration. A browser on one network may successfully connect using an IPv4 address; another network may attempt IPv6. Address-family selection and fallback depend on client and network behavior, not on an unconditional DNS rule that AAAA is preferred. IPv4 example allocation IPv6 example allocation
Compare the two record types
| Criterion | A | AAAA |
|---|---|---|
| Address family | IPv4 | IPv6 |
| Payload | One 32-bit address | One 128-bit address |
| Example value | 192.0.2.25 | 2001:db8::25 |
| DNS owner | Can be www.example.com | Can be that same name |
| Main check | IPv4 reachability and server configuration | IPv6 reachability and server configuration |
A record set may contain multiple addresses. Having a syntactically valid AAAA record does not mean the IPv6 endpoint is reachable from the public Internet or configured to serve the hostname. Equally, deleting AAAA simply to hide a routing problem may harm clients that use IPv6; investigate first.
In practice
When some visitors can open a site and others cannot, compare A and AAAA answers separately and ask whether the origin or CDN listens on both advertised address families. A DNS response alone cannot show the HTTP status, TLS certificate or network route. Obtain actual approved destination addresses from the hosting provider and validate HTTPS for the intended hostname before changing records.
For connection setup consult Connect a domain to a website. If the site only fails for certain visitors, follow A website works for some visitors only, not an assumption that either address family must always win.
Sources & model boundaries
Primary references used for this explanation. The example above is illustrative; it is not a live check.
- RFC 1035 — Domain Names: Implementation and Specification
Sections 3.2, 3.3 and 4. RR formats, TTL, A, NS, SOA, CNAME and MX records.
Checked .
- RFC 3596 — DNS Extensions to Support IPv6
Sections 2 and 3. AAAA records and their IPv6 address data.
Checked .
- RFC 5737 — IPv4 Address Blocks Reserved for Documentation
Sections 3–4. TEST-NET IPv4 address examples are documentation-only.
Checked .
- RFC 3849 — IPv6 Address Prefix Reserved for Documentation
Sections 2–3. 2001:db8::/32 is documentation-only IPv6 space.
Checked .