Low TTL DNS
Shorter TTLs for controlled failovers and migrations.
Cached DNS answers can delay a migration or failover. Plan record lifetimes ahead of the change so clients can discover the updated destination sooner.
Cloud DNS Growth and Business support a one-second minimum TTL. Configure TTLs per record, alongside health checks and routing policies. Actual failover timing also depends on health detection and resolver caching.
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.
One-second minimum TTL
Available on Growth and Business for records that need frequent changes.
Anycast that can take the queries
Low TTLs mean more queries. 210+ servers are the reason that is viable.
Per-record control
Keep MX and static records high. Lower the records you actually move.
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.
- 1Inventory records that must move quickly
Application apex, CDN hostnames, failover targets.
- 2Lower those TTLs ahead of the change
Do it before the maintenance window, not during it.
- 3Make the change
Update records, weights or health-check eligibility.
- 4Raise TTLs afterwards if you want
Static records do not need to stay at one second forever.
Outcomes
What changes once the hostname is on Aptranet.
- Critical records can use a 1-second TTL
- Shorter cache lifetimes for planned migrations
- Static records can keep higher TTLs
- Query load is absorbed on Anycast
Keep reading
Related pages
More DNS use cases on the same Cloud DNS footprint.
Frequently asked questions
No. Some recursive resolvers clamp TTLs. Still lower them: many will honour a short TTL, and health-aware answers help the rest.
Lookups happen more often. Anycast Cloud DNS is built for that. The application handshake is still the larger cost.
No. Use low TTLs where you need change. Leave stable records longer.
Yes, with signature lifetimes planned so validation and low TTLs remain compatible.