IPv6 DNS
IPv6 is a DNS record and a DNS transport.
Applications that added IPv6 still publish only A records, or host DNS on IPv4-only nameservers, so dual-stack clients never see the path.
Cloud DNS supports IPv4 and IPv6 records and transport. Publish AAAA beside A, and serve the zone from Anycast nameservers that speak both.
Why teams use Aptranet
What IPv6 DNS looks like on this network.
Cloud DNS answers on 210+ Anycast servers, with GeoDNS, health checks and a one-second minimum TTL for change.
AAAA records on Anycast
Dual-stack applications can be published without a second DNS vendor.
IPv6 nameserver transport
Resolvers can query authority over IPv6 as well as IPv4.
Same steering as IPv4
GeoDNS, weights and health checks apply to the records you publish, including AAAA.
How to set it up
A cutover you can validate before DNS moves.
Create the Cloud DNS configuration, prove it on an Aptranet hostname, then point production DNS when the path looks correct.
- 1Add AAAA records for dual-stack endpoints
Only for infrastructure that actually speaks IPv6.
- 2Health-check the AAAA targets
Do not publish an address you cannot probe.
- 3Delegate with IPv6-capable NS
Cloud DNS Anycast nameservers support IPv6.
- 4Verify from an IPv6 client
Confirm both lookup transport and application connectivity.
Outcomes
What changes once the hostname is on Aptranet.
- AAAA records can go live beside A
- Authority is reachable over IPv6
- Steering policies include IPv6 targets
- Health checks can watch AAAA endpoints
Keep reading
Related pages
More DNS use cases on the same Cloud DNS footprint.
Frequently Asked Questions
No. Publish AAAA when the endpoint you return actually accepts IPv6. Cloud CDN can still deliver over IPv6 to clients.
Yes. Sign the zone, including AAAA records.
Policies apply to record sets. Design IPv4 and IPv6 maps so they do not disagree in surprising ways.
Vanity nameservers are supported. Include AAAA glue where the parent requires it.