How to Configure an AAAA Record: Step-by-Step for Every Major Provider
Adding the record itself takes thirty seconds. Doing it correctly — with the right TTL, the right verification, and the right infrastructure already IPv6-ready — is what actually separates a clean rollout from a support ticket.
Before You Touch DNS: Confirm Infrastructure Readiness
The single most common cause of a bad AAAA rollout isn't a DNS mistake at all — it's adding the record before the actual infrastructure behind it is ready. Publishing an AAAA record makes a promise: "this hostname is reachable over IPv6." If the server, load balancer, or CDN configuration behind it isn't genuinely listening on IPv6 yet, that promise is broken the moment an IPv6-preferring client tries to connect, and depending on Happy Eyeballs timing, that failure can range from a slightly slower connection to an outright timeout for some clients.
Before adding anything to DNS, confirm three things: the server or service actually has a valid, routable IPv6 address assigned; the firewall or security group rules for that service have been mirrored to permit the same traffic over IPv6 that's permitted over IPv4; and, if this is a load-balanced or CDN-fronted service, that the front-end layer itself has IPv6 support enabled — many CDNs and load balancers treat this as an explicit opt-in setting rather than an automatic default.
Step-by-Step: The Universal Workflow
Find Your Server's IPv6 Address
Confirm the exact IPv6 address assigned by your hosting provider — check your server's network configuration or hosting dashboard directly rather than guessing or reusing an example address from documentation.
Open Your DNS Provider's Record Editor
Log in to whichever service actually manages your domain's DNS zone — this might be your registrar, a dedicated DNS provider like Cloudflare, or a cloud platform's DNS service.
Add a New AAAA Record
Select AAAA as the record type, enter the exact hostname (or @ for the apex domain), paste in the IPv6 address, and set a reasonable TTL — 3600 seconds (one hour) is a sensible default for most production use.
Save and Allow for Propagation
The record itself typically becomes live at your authoritative nameserver within minutes, but resolvers worldwide won't reflect the change until any previously cached negative or different answer's TTL expires.
Verify With a Live Lookup
Confirm the record resolves to the exact address you expect using a live tool — don't rely on your own device's cached DNS resolver, which may not reflect the freshest answer.
Cloudflare
In the Cloudflare dashboard, navigate to the DNS management section for your domain, click Add Record, select AAAA as the type, enter the hostname and IPv6 address, and choose whether to enable the orange-cloud proxy. With the proxy enabled, Cloudflare can serve IPv6 to visitors at its edge even if your actual origin server only supports IPv4 internally — genuinely useful for a quick win, but worth remembering that this doesn't make your origin itself IPv6-capable, only the path between visitors and Cloudflare's edge.
AWS Route 53
In Route 53, open the hosted zone for your domain, click Create Record, select AAAA from the record type dropdown, and enter the value directly, or — for AWS-native resources like an Application Load Balancer or CloudFront distribution — use an Alias record instead, which Route 53 automatically keeps synchronized with the target resource's current IPv6 address without requiring manual updates when that address changes.
Google Cloud DNS
Within Google Cloud DNS, open the relevant managed zone, click Add Record Set, select AAAA as the resource record type, enter the hostname and IPv6 address, and set the TTL. The workflow mirrors adding an A record almost exactly, just with the different record type selected and an IPv6 address in the value field.
Azure DNS
In the Azure portal, navigate to your DNS zone resource, select Add Record Set, choose AAAA as the type, and supply the hostname and IPv6 address. Azure DNS also integrates with Traffic Manager for dual-stack routing scenarios where traffic needs to be distributed across multiple IPv6 (and IPv4) endpoints based on routing method — useful for larger, geographically distributed deployments.
Registrar-Level DNS Panels (GoDaddy, Namecheap, and Similar)
Most registrar DNS panels follow the same basic pattern: locate the DNS management section for your domain, add a new record, select AAAA as the type, and fill in the hostname and IPv6 address fields. The interface details vary by registrar, but the underlying record you're creating is identical regardless of which panel you're using.
Verifying the Record After Saving
Once saved, don't assume it's correct — verify. A live lookup confirms the exact address currently being served, catches typos before they reach production traffic, and — critically — confirms whether the record has actually propagated to public resolvers yet or is still limited by a previous record's remaining TTL. Check with our AAAA Record Lookup tool, or from a terminal with dig AAAA yourdomain.com +short.
Common Configuration Mistakes
| Mistake | Consequence |
|---|---|
| Entering an IPv4 address in the AAAA field | Most DNS panels will reject this outright with a validation error, but some accept malformed input silently |
| Forgetting to update firewall rules for IPv6 | The record resolves correctly but connections fail or hang, since nothing is actually listening/permitted on that address |
| Setting an extremely long TTL before testing | Makes it painfully slow to roll back a mistake — use a short TTL during initial testing, lengthen it after confirming stability |
| Not verifying with a live lookup after saving | Typos or copy-paste errors in a 128-bit address are easy to make and easy to miss without direct verification |
| Assuming a proxied CDN record means your origin is IPv6-ready | A CDN can synthesize IPv6 at its edge without your actual backend server supporting it at all |
Best Practices for a Clean Rollout
Start with a short TTL (300 seconds) while testing, and lengthen it to a standard production value (3600 seconds or more) only after confirming the configuration is stable. Roll out to a low-traffic subdomain before touching the apex domain. Always verify with a live lookup rather than trusting the dashboard's saved-successfully confirmation alone. And treat the DNS record as the last step in a rollout, not the first — infrastructure readiness, firewall parity, and monitoring coverage should all be confirmed before the record goes live publicly.
Related Tools
Verify your new record instantly with AAAA Record Lookup. Check the corresponding IPv4 A record with A Record Lookup, confirm global propagation with DNS Propagation Checker, or review the full record set for the domain with DNS Lookup. If something isn't behaving as expected after configuring, see our AAAA Troubleshooting guide next.
FAQ
dig AAAA yourdomain.com +short from a terminal.ToolsNovaHub tools are built and independently maintained with a focus on accurate, no-signup network and security utilities. Spotted an error? Let us know.
📋 Related Tools & Guides Comparison
| Resource | Type | Link |
|---|---|---|
| AAAA Record Lookup | Tool | Open Tool → |
| DNS Propagation Checker | Tool | Open Tool → |
| DNS Lookup | Tool | Open Tool → |
| AAAA Troubleshooting | Guide | Read Guide → |