multi-region DNS
A multi-region app still starts with a DNS answer.
Running application stacks in more than one region does nothing if every resolver still receives the first region you launched.
Publish regional endpoints in Cloud DNS. Use GeoDNS or weights to steer, health checks to drop a failed region, and low TTLs so the map can change.
Why teams use Aptranet
What multi-region 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.
Region-aware answers
GeoDNS sends resolvers toward nearby application endpoints.
Region failure is a DNS event
Health checks can remove a region from eligible answers.
Controlled cutovers
Weights and one-second TTLs support planned region evacuations.
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.
- 1Give each region a stable endpoint
Addresses or hostnames that Cloud DNS can return.
- 2Steer with GeoDNS or weights
Match how you actually deployed capacity.
- 3Health-check every region
Do not wait for humans to edit records during an incident.
- 4Rehearse evacuating a region
Fail a check or drop a weight and confirm traffic moves.
Outcomes
What changes once the hostname is on Aptranet.
- Resolvers can receive a nearby region
- A failed region can leave the answer set
- Planned evacuations do not need a ticket on TTL
- Authority itself is multi-location Anycast
Keep reading
Related pages
More DNS use cases on the same Cloud DNS footprint.
Frequently Asked Questions
Useful for debugging. The public name can still be one record set that steers between regional targets.
It complements them. DNS chooses a target. Anycast applications announce the same address from many places.
GeoDNS can steer toward in-region endpoints. It is not a legal control by itself. Design the application accordingly.
CDN PoPs already distribute delivery. Multi-region DNS is for application or origin endpoints behind or beside the CDN.