Images are AI-generated editorial illustrations, not documentary photographs or verified product screenshots.
DNS AAAA records map names to IPv6 addresses
DNS AAAA records associate a hostname with an IPv6 address. Cloudflare distinguishes them from A records, which associate names with IPv4 addresses. Adding an AAAA record is therefore a routing decision, not simply a cosmetic modernization of the DNS zone. The destination must actually serve the intended application over IPv6. Keep existing values and coordinate the change with the hosting or network provider.
Confirm the destination before publishing
Obtain the IPv6 address from the responsible provider and confirm which hostname it should serve. Check the web server, firewall, application routing and certificate configuration for that path. Do not turn a random IPv4 address into an assumed IPv6 equivalent or borrow an address from a tutorial. If a proxy or CDN manages the public records, understand its documented behavior instead of treating its addresses like direct origin-host settings.
Understand the relationship with A records
A and AAAA records can provide different address-family routes to the same named service. Their existence does not mean every visitor will use the same route or experience identical reachability. A working IPv4 path can hide an IPv6 problem during a limited test. Keep both configurations understandable and use suitable tests to confirm which address family is actually being exercised.
Test reachability and application behavior
Validate the record at the authoritative DNS source and through relevant public resolution. Then test the actual HTTPS page, redirects and affected functions over IPv6 where supported. An answer from DNS proves a record can be returned; it does not prove the destination accepts the connection. Check server-side evidence with the host if some visitors see intermittent failures or if one address-family route behaves differently.
Maintain a safe change and recovery record
Document the old value, new value, reason, approver and verification result. Account for DNS caching when comparing observations after a change. If IPv6 service is not yet configured, resolve that dependency rather than publishing an untested route solely to satisfy a checklist. Monitor the result and coordinate corrections with the provider. Removing a record may also take time to affect cached answers, so do not promise an instantaneous universal recovery.
Common questions
Is an AAAA record an IPv4 record with a different name? No; it contains an IPv6 address. Does adding it guarantee better speed? No; actual network and service behavior determine the result. Should the AAAA path be tested even when the site already works over IPv4? Yes, because that existing test may not exercise IPv6.
Sources and further reading
cloudflare.com: dns aaaa record