GeoDNS

Route users with Aptranet Cloud DNS GeoDNS by continent, country, coordinates, ASN, IP or subnet on 210+ Anycast DNS servers.

210+Anycast DNS servers
210+Points of presence worldwide
1 secondMinimum TTL
30 msAverage network latency

GeoDNS

The DNS answer can depend on where the resolver is.

A single A or AAAA record sends every resolver to the same endpoint. Applications that run in more than one region need the answer to change with location, ASN or subnet.

Cloud DNS GeoDNS returns different records by coordinates, continent, country, ASN, IP or subnet. Health checks can remove endpoints that are down from eligible answers.

Why teams use Aptranet

What GeoDNS looks like on this network.

Cloud DNS answers on 210+ Anycast servers, with GeoDNS, health checks and a one-second minimum TTL for change.

More than country steering

Steer by coordinates, continent, country, ASN, IP or subnet — not a single geo bucket.

210+ Anycast DNS servers

Resolvers reach a nearby authoritative server, including during traffic events.

Health-aware answers

Unhealthy endpoints can be taken out of the eligible GeoDNS set.

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.

  1. 1
    Host the zone on Cloud DNS

    Delegate the domain to Aptranet Anycast nameservers.

  2. 2
    Define location policies

    Map continents, countries, ASNs or subnets to application endpoints.

  3. 3
    Attach health checks

    Remove non-responsive endpoints from the answers resolvers receive.

  4. 4
    Use a low TTL while you iterate

    Cloud DNS supports a one-second minimum TTL for planned changes.

Outcomes

What changes once the hostname is on Aptranet.

  • Resolvers can receive a nearby endpoint
  • ASN and subnet splits are available
  • Unhealthy targets can be excluded
  • Policy changes propagate quickly

Frequently Asked Questions

Authoritative DNS sees the recursive resolver. GeoDNS uses that view, which is usually close to the user but not identical.

Yes. Weighted load balancing and GeoDNS can be used together depending on the record set.

No. GeoDNS chooses which endpoint name or address is returned. Application anycast is a separate routing design.

Subnet and IP policies support finer splits than continent or country maps.

Put GeoDNS on the Aptranet edge.

Get started in the Management Console, or talk through origin, DNS and cutover with Aptranet.