Fill the Server: 80% off your first 4 monthly invoices, monthly billing. Ends Nov 30, 2026. 25 spots in this batch.FILL25
Fill the Server, annual: about 29.63% off your first annual invoice. Ends Nov 30, 2026.FILL25Y
Fill the Server, 2 year term: about 15.69% off your first biennial invoice. Ends Nov 30, 2026.FILL25B
Fill the Server, 3 year term: about 11.11% off your first triennial invoice. Ends Nov 30, 2026.FILL25T
80% off your first 3 months, monthly billing. Ends Dec 25, 2027.3MONTHS80
50% off your first annual Shared term. Ends Dec 31, 2027.50SHARED
Shared Starter, 3 year term: C$105.84 total.MOOSE294
20% off your first 3 monthly VPS invoices. Ends Dec 31, 2027.20VPS3
25% off your first annual base VPS term.25VPS

← All guides

DNS

DNS TTL explained: how cache time affects changes

Published August 2026 · 7 min read

Time to Live is the cache lifetime attached to a DNS answer. A lower TTL can make planned changes become visible to refreshing resolvers sooner, while a higher TTL reduces repeated authoritative queries and keeps stable answers cached longer.

TTL affects caches that fetch the record after the value is set

If a resolver already cached an answer with a long TTL, lowering the TTL at the authoritative server does not retroactively shorten that existing cache. Lower it ahead of a planned move and wait for old caches to expire.

Use low TTL temporarily for high-change windows

Before a controlled migration, a shorter TTL can reduce the period during which users receive the old address. After the destination is stable, return to a normal TTL after the destination is stable.

Rollback also follows cache behaviour

A short TTL helps only resolvers that are allowed to refresh. If you switch back after a failed cutover, some clients may still hold whichever value they cached most recently until that TTL expires.

Nameserver delegation has its own caching considerations

Record TTL planning does not make an authoritative nameserver migration instantaneous. Delegation and nameserver address information can have separate caches, so plan provider moves more carefully than a single A-record change.

Next step

DNS TTL tells recursive resolvers how long an answer may be cached. Learn how TTL affects planned migrations, query load, rollback timing, and why lowering it at the last second does not clear old caches.

Read more DNS guides

Keep reading

Related guides.

CAA record planning: control which certificate authorities may issue for a domain

Plan CAA records around the certificate providers you use, subdomains and incident contacts, then verify issuance will still work before enforcing restrictions.

Read the guide

CNAME chain problems: why extra DNS aliases can break or slow resolution

Trace CNAME chains, loops, missing terminal records and provider restrictions, then shorten unnecessary aliases without changing the intended hostname.

Read the guide

DKIM selector rotation: change signing keys without breaking verification

Rotate DKIM selectors by publishing the new key first, switching signers, monitoring authentication and retaining the old selector long enough for queued mail.

Read the guide

More domains & dns guides

We will handle the move. You check it first.

Your current site stays online until your new one is ready. You approve the copy first, and if anything is not right we switch you back right away. The price you pick is the price you renew at.

Start my free moveSee plans and prices
See pricesFree move