What TTL is and when to lower it before a move

TTL, or Time To Live, is a number attached to every DNS record that tells resolvers how many seconds they may cache the answer before checking again. Lowering the TTL a day or two before you move a site to a new server or new IP is what makes the switch feel fast: once the record actually changes, resolvers pick it up quickly instead of serving a stale answer for hours. This is especially useful when you migrate to a dedicated Class C IP, because you want visitors and crawlers landing on the new address as soon as it is ready.

What TTL actually controls

TTL is expressed in seconds and lives on individual records: your A record, CNAME, MX, and so on. When a resolver looks up your domain, it stores the answer and reuses it until the TTL expires. A record set to 3600 can be cached for one hour; a record set to 300 for only five minutes. The TTL does not change how your site works day to day, it only changes how long the internet remembers an old answer after you edit the record.

Why you lower TTL before a move

Imagine your A record points at the old IP with a TTL of 86400 (24 hours). If you change the IP without preparing, some resolvers keep sending traffic to the old server for up to a full day. That window can mean broken pages, split traffic, and confusing analytics. By dropping the TTL to a small value ahead of time, you shrink that window to minutes, so the cutover is nearly seamless.

How to lower TTL in cPanel

You edit TTL in the zone editor. Do this at least as long before the move as the current TTL, so old cached copies have time to age out.

1. Open cPanel and go to the Domains section, then click Zone Editor.
2. Find the domain you are moving and click Manage.
3. Locate the records you will change during the move, typically the A record for the root and www, and any CNAME or MX records involved.
4. Click Edit on each record and set the TTL to a low value such as 300 (5 minutes) or 600 (10 minutes).
5. Save each record and wait for the old TTL period to fully elapse before you start the migration.

A typical timeline looks like this: current TTL is 86400, so you lower it to 300 a full day in advance, wait 24 hours, then perform the actual IP change. Because the record is now cached for only five minutes, resolvers worldwide converge on the new address almost immediately.

Raise it back after the move

A permanently low TTL means more repeated lookups and a little extra load, with no real benefit once the address is stable. After you confirm the site is live and healthy on the new IP, edit the same records and return the TTL to a normal value like 3600 (1 hour) or 14400 (4 hours). Lower TTL for change windows, higher TTL for steady state.

Records worth pre-lowering

• A and AAAA records when the server or IP changes.
• CNAME records that alias to a hostname you are repointing.
• MX records if you are also moving mail, so delivery follows the new server quickly.

If you are moving to a dedicated Class C IP setup, planning the TTL ahead of time keeps the transition clean and your footprint controlled. For the full record set and account details, our DNS and IP management guides walk through each record type, and you can reach us any time through contact us to coordinate a migration window. The formal definition of TTL and related DNS terminology is documented in RFC 9499.