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

Domains & DNS

DNS TTL planning: choose cache times before a change or migration

Published August 2026 · 2 min read · Updated 2026-09-05

DNS TTL planning controls how long recursive resolvers may reuse an answer before asking again. TTL is not a universal propagation timer and it does not guarantee every cache disappears at the same instant. Plan it around change risk, resolver load, and how quickly rollback must become visible.

Start with the current authoritative TTL

Inspect the exact A, AAAA, CNAME, MX, or other record that will change and record its current TTL before editing. A lower TTL only helps after existing caches containing the old higher TTL have naturally expired.

For a planned migration, lower the TTL far enough in advance that the previous value no longer controls most recursive caches when the cutover begins.

Use different TTLs for different stability needs

Stable infrastructure records can reasonably cache longer than records being actively migrated. Very low TTLs increase query load and do not fix incorrect authoritative data.

Email MX, verification TXT, DKIM keys, and service discovery records may have different change cadence from a website address. Do not reduce the entire zone blindly.

Plan rollback using cache behavior

If the new destination fails and you restore the old record, recursive resolvers may still hold either answer until its TTL expires. Keep both source and destination healthy during the overlap when the service allows it.

For stateful applications, DNS rollback does not synchronize newer database writes back to the old environment.

Restore a normal TTL after the move

Once the destination is stable and old caches have expired, return records to a sensible normal TTL. Keep the migration timestamp, old/new values, and final authoritative answer in the change record.

  • Lower TTL before the maintenance window.
  • Change only records involved in the move.
  • Keep both sides available through cache overlap.
  • Raise TTL again after verification.

Next step

Use DNS TTLs deliberately before cutovers, understand resolver caching, and avoid last-minute changes that leave old answers circulating longer than expected.

Explore DotMoose domains and DNS

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