Health checks

Monitor endpoints continuously with Aptranet Cloud DNS health checks and remove non-responsive infrastructure from eligible DNS answers.

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

DNS health checks

Connect endpoint health to the record resolvers receive.

Static DNS will keep handing out an address after the application behind it is gone. Operators should not be the health check.

Cloud DNS health checks monitor configured endpoints and use that state so non-responsive infrastructure is left out of eligible answers.

Why teams use Aptranet

How it works with Aptranet

Cloud DNS combines Anycast resolution with traffic steering and health checks. Growth and Business support TTLs as low as one second.

Continuous endpoint monitoring

Checks run against the targets you configure, not against a single probe region you forgot.

Answers follow health

GeoDNS and weighted pools can exclude unhealthy endpoints automatically.

Pairs with a 1-second TTL

Once health changes, resolvers can pick up the new answer quickly.

How to set it up

Validate your setup before production changes.

Configure your Cloud DNS zone and verify its records and routing policies. Test answers from the authoritative nameservers before changing your domain delegation.

  1. 1
    Choose what to probe

    HTTP, HTTPS or the check type that matches how the endpoint should be considered up.

  2. 2
    Attach checks to record sets

    Only endpoints that pass remain eligible.

  3. 3
    Set a TTL that matches failure RTO

    Health without a usable TTL still leaves resolvers on a cached dead answer.

  4. 4
    Alert on check failures

    DNS failover is not a substitute for knowing that a region is down.

Outcomes

What changes once the hostname is on Aptranet.

  • Dead endpoints can leave DNS automatically
  • Geo and weighted policies honour health
  • TTLs can be low enough to matter
  • Operators still see the failure

Frequently asked questions

Design check sensitivity so transient blips do not churn answers. Rehearse failure in staging.

No. Health checks decide DNS eligibility. Application monitoring still explains why a target failed.

Plan the empty-set behaviour with Aptranet. Do not assume DNS can invent a healthy target.

Cloud DNS supports IPv4 and IPv6 records. Probe the addresses you actually publish.

Put Health checks to work with Aptranet.

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