DNS load balancing

Balance traffic with Aptranet Cloud DNS weighted and subnet load balancing, GeoDNS and health checks on Anycast authority.

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

DNS load balancing

Load balancing can start before the TCP handshake.

Application load balancers only see connections that already arrived. DNS is the first chance to split traffic across regions, pools or canaries.

Use weighted records, subnet load balancing and GeoDNS so each resolver gets the intended endpoint. Health checks keep dead pools out of the rotation.

Why teams use Aptranet

What DNS load balancing looks like on this network.

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

Weighted traffic splits

Send 10% of answers to a new pool, then raise the weight as it proves in.

Subnet load balancing

Finer splits than continent or country when you know the resolver space.

Health-informed rotation

Unhealthy endpoints are removed from eligible answers.

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
    Identify the pools

    Regions, clusters or canary endpoints that can receive traffic.

  2. 2
    Set weights or subnets

    Start conservatively on a new pool.

  3. 3
    Attach health checks

    Do not wait for operators to notice a dead pool.

  4. 4
    Watch query and origin metrics

    Confirm the split matches what you intended, then adjust weights.

Outcomes

What changes once the hostname is on Aptranet.

  • Traffic can be split in DNS
  • Canaries do not need 50% of answers
  • Dead pools can disappear automatically
  • Subnet policies support tighter control

Frequently Asked Questions

No. Resolvers cache answers and represent many users. Use it for coarse splits and region steering, not per-request fairness.

Yes. DNS chooses a pool. The load balancer still spreads connections inside that pool.

Yes. DNS can steer to more than one CDN or origin hostname. Cloud CDN origin groups handle delivery-side failover.

Low enough to change weights on your schedule. Cloud DNS supports a one-second minimum TTL.

Put DNS load balancing on the Aptranet edge.

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