Quick answer
TTL describes how long DNS answers may be cached. Lowering it before a planned record change can shorten some future cache retention, but it does not immediately remove answers already cached under the old value.
Before you start
Identify the authoritative DNS provider and the exact records changing. Record their current values and TTLs, plus the planned cutover and rollback. Keep email and verification records outside the change unless the plan explicitly includes them.
Steps
- Read the old TTL early enough to allow existing caches to age out. If the provider permits a lower value, change only the intended record TTL in advance.
- Verify the updated TTL and values at the authoritative provider. For proxied services or provider-managed records, respect their fixed or automatic TTL behavior.
- At cutover, change the approved destination and compare authoritative answers with recursive resolvers. Keep the old site available during the transition if the release plan requires it.
- After stability is demonstrated, return TTLs to a suitable normal value and retain the before/after record of the change.
Verify the result
The authoritative answer should match the approved destination while different caches converge. Website, certificate, proxy, and browser caches can introduce separate behavior that TTL alone does not explain.
Troubleshooting and recovery
If visitors split between old and new sites, compare actual DNS answers and cache timing rather than repeatedly changing records. Reversing a DNS value also takes time to reach cached clients.
Related help
- Find where your domain's DNS is managed before changing records
- Change nameservers without losing email and verification records
- Check website and email behavior after a migration
Official references
Reviewed October 31, 2026. Interfaces, vendor availability, and account features can change. Check your current account before making changes.
