TTL strategy for cutovers

A TTL strategy for cutovers means lowering your A and AAAA record TTLs a day ahead, waiting out the old TTL fully, changing the records, watching resolution, and then raising the TTL again. That sequence is what lets caches converge on the new addresses without leaving visitors on the old ones longer than necessary.

Plan the window before you change anything

Write three checkpoints on a note: T-24h, T-0, and T+24h. At T-24h, drop the A and AAAA TTL to 300 seconds, or to 60 if the zone is small and you will be available to watch it. Then wait for the previous TTL to expire everywhere that matters. If the old TTL was 86400 and you lower it in the morning and switch in the afternoon, many caches still hold the old value for the rest of that day. At T-0, update the addresses. Check your authoritative nameserver first, then a public resolver. At T+24h, raise the TTL back to something steady such as 3600 or 14400. The NS TTL at the TLD is separate from the A TTL, so this approach does not speed up a nameserver change.

dig example.com A +ttlunits @ns1.logicweb.com

The answer from ns1.logicweb.com shows the authoritative TTL you just set. A recursive resolver shows the remaining TTL still held in that cache. If ns1 reports 300 and a public resolver still reports a much larger number, that cache has not expired yet. Wait it out. Avoid flipping the A record every few minutes, because that only spreads more versions into the wild.

Keep short TTLs temporary

Leaving records at 60 seconds as a permanent habit adds needless load and does not clear caches that already stored the old data. Mail needs the same care: if MX is moving, lower the MX TTL on the same timeline. Greylisting can still delay retries on a schedule you do not control. Do not lower every record in the zone for agility. SOA, NS, and DKIM selectors are better left stable unless you have a clear reason to change them.

A registrar transfer runs on a different clock. See domain transfer, lock, and EPP for that process. Lowering TTL will not make a transfer finish faster.

What to verify after the change

After you publish the new A or AAAA values, confirm ns1.logicweb.com and ns2.logicweb.com both return them with the short TTL you set. Then check a public resolver and wait until its remaining TTL drains and the new answer appears. Once traffic looks clean for a day, restore a longer TTL so day-to-day lookups stay efficient.