You move your website to a new host, update the DNS record and check the site. It still shows the old version. Your colleague, across town, sees the new one. A customer emails to say the site seems broken. Nothing is actually wrong. You are watching DNS propagation happen, and understanding it can save a lot of worry.
Why DNS answers get remembered
When someone visits your domain, their device asks a DNS resolver, often run by their internet provider or a public DNS service, where to find it. Looking up the answer from scratch involves several steps, so resolvers remember answers for a while. That memory is a cache, and it makes the internet much faster. It also means that after you change a record, resolvers around the world keep handing out the old answer until their remembered copy expires.
The process of old answers expiring and new ones taking their place is what people call propagation. It is less like a message spreading outward and more like many separate clocks running out at different times.
What TTL controls
Each DNS record has a TTL, which stands for time to live. It is a number of seconds that tells resolvers how long they may keep the answer before asking again. A TTL of 3600 means an hour. A TTL of 86400 means a day.
Longer TTLs reduce lookups and can make normal browsing slightly more efficient. Shorter TTLs mean changes take effect more quickly. Most of the time, a moderate TTL is fine. The value matters most just before you make a change.
Planning a change with TTL in mind
If you know a change is coming, such as a hosting move or a new email provider, lower the TTL on the affected records ahead of time. A typical approach looks like this:
- At least one full current TTL period before the change, lower the TTL to a short value, such as a few minutes.
- Wait for the old, longer TTL to expire everywhere.
- Make the change. Most resolvers will pick it up quickly.
- Once everything is stable, raise the TTL back to a normal value.
Lowering the TTL also makes it easier to reverse course if something goes wrong. Some DNS providers have minimum TTL values or handle certain records differently, so check your provider’s documentation.
Other places changes can hide
Not every delay is DNS. When changes seem slow, consider:
- Your own device. Computers and browsers keep their own DNS caches. Restarting the browser or device, or trying a phone on mobile data, can help.
- Website caches. Page caching and CDNs can show old content even after DNS updates.
- Nameserver changes. Changing which company runs your DNS entirely, rather than editing a record, can take longer, because records at the domain registry level often carry longer TTLs.
Keep both sides working during the change
Because some visitors will reach the old server and some the new one for a while, keep the old hosting running until the change has fully settled. Avoid making content changes on the old site during that window. With a little planning, propagation becomes a non-event rather than a source of alarm.
A Worked Example: Moving to New Hosting
Here is how the TTL plan looks in practice for a small business moving its website from one host to another, while keeping email where it is.
- Two days before the move: the web team checks the current TTL on the website’s records and finds it set to a full day. They lower it to a few minutes and note the original value.
- The day after: a full day has passed, so resolvers that cached the old, long TTL have now expired it and picked up the short one.
- Move day: the new site is ready on the new host. The team updates only the website records to point to the new server. Mail records are left untouched.
- Within minutes to an hour: most visitors begin reaching the new site. A few may still see the old one briefly.
- A few days later: with everything stable, the team raises the TTL back to a normal value and updates the website documentation.
The key decision in that example is what not to change. Email records, verification records for other services and any records for subdomains stay exactly as they were, unless the move specifically requires changing them.
How to Check What the World Is Seeing
When you want to know whether a change has taken effect, a few simple checks help:
- Use an online DNS lookup tool. Many free tools query resolvers in different regions and show which answer each one returns. If most show the new address, propagation is well along.
- Try a phone on mobile data. It uses a different network and resolver than your office connection, which gives you a second view.
- Use a private browsing window. This avoids some browser caching, though it does not clear your device’s DNS cache.
- Ask your web team to check directly. They can query your DNS provider’s servers to confirm the record itself is correct, separate from what any cache says.
Mistakes That Turn Propagation Into a Problem
- Changing nameservers when only a record needed changing. Moving your entire DNS to a new provider can drop records that were never copied over, including email. Copy and compare every record first.
- Forgetting the www version. The bare domain and the www address may be separate records. Update both.
- Canceling the old host on move day. Visitors still reaching the old server will find nothing. Keep it running until the change has settled.
- Editing content on the old site during the switch. Changes made there may be lost. Pause updates until the move is complete.
- Not writing down the original records. A saved export or screenshot of your DNS before the change makes it far easier to reverse.
Questions Owners Ask
How long does propagation take?
It depends mostly on the TTL of the records involved. With a short TTL set ahead of time, many visitors see a change within minutes. With a long TTL, it can take as long as that TTL, and nameserver changes can take longer.
Can we force everyone to see the change now?
Not across the whole internet. You can clear caches on your own devices, but other people’s resolvers will update on their own schedule. That is why lowering the TTL in advance is so useful.
Should we keep the TTL short permanently?
Usually there is no need. A moderate TTL works well day to day. Lower it ahead of planned changes, then raise it again afterward.




