Quick answer: Lower the TTL of the records you plan to change to 300 seconds at least a day in advance, keep the old server running until traffic fully moves, and only then change the A record. This shrinks the visible "propagation" window from hours to minutes.
Overview
DNS "propagation" is really just caching: resolvers keep your old record until its TTL expires. You cannot force other people's caches to refresh, but you can plan around them so visitors never notice a migration.
Before you start
- Know the current TTL of the records you will change:
dig A example.comshows it as the second column. - A migration plan where both old and new servers can serve the site for a transition period.
Step-by-step guide
- 24–48 hours before the switch: set the TTL of the affected A/AAAA records to
300(5 minutes). The old, longer TTL must expire everywhere first — hence the lead time. - Prepare and test the site on the new Cloud2Y server (use a hosts-file override to preview it before DNS changes).
- Switch: update the A record to the new IP (how).
- Watch traffic move — within ~5 minutes most resolvers pick up the new value:
dig +short A example.com @1.1.1.1
dig +short A example.com @8.8.8.8- Keep the old server (or a redirect on it) alive for at least a day for stragglers, then decommission and raise the TTL back to
3600or more.
Common issues
- TTL lowered at the same moment as the switch: pointless — caches still hold the old record with the old TTL.
- Old server shut down immediately: visitors on stale caches see downtime; keep it running through the overlap.
- ISP resolvers ignoring tiny TTLs: a few clamp to minutes or hours — you cannot fix these, only wait.
When to contact support
Migrating a site to Cloud2Y and want the cutover checked end-to-end? Open a ticket — we can verify the new server is ready before you flip the record.
Frequently asked questions
Why lower the TTL before a migration?
The TTL controls how long resolvers cache your record. Dropping it to 300 seconds a day in advance means that after the switch, caches refresh within five minutes instead of hours.
Can I force DNS propagation to happen faster?
No — caches on other people's resolvers cannot be flushed remotely. You can only prepare with a low TTL beforehand and keep the old server running during the overlap.
When can I safely shut down the old server?
After at least one full old-TTL period, once logs on the old server show no meaningful traffic. Keeping it up for a day is a cheap way to guarantee zero downtime.
Related articles
- How long does DNS propagation take?
- How to point a domain to Cloud2Y VPS
- How to update an A record
- Common DNS mistakes
Ready to get started? Order a VPS at Cloud2Y →
