DNS Propagation: How Long It Takes and Why Delays Happen When Moving a Site

You moved your site to new hosting, changed the nameservers, and… the old version still shows up in your browser. This is the moment when many people start to panic, convinced they broke something. The good news: it is not a malfunction, it is simply DNS propagation. The natural question is how long DNS propagation takes and why, sometimes, it seems to drag on forever. Let us clear up what happens behind the scenes, so you know exactly what to expect when you move your WordPress site.

What DNS propagation actually is

DNS is like the internet’s address book: it translates your domain name (for example, your-site.com) into the IP address of the server where the site actually lives. When you move your site to different hosting, that is precisely the address you change. Think of it as a change of postal address: it takes a while until every courier learns where you moved.

The catch is that the answer does not always come straight from the source. Internet providers, browsers, and thousands of DNS servers around the world cache the old answer for a while, so they can respond faster next time. DNS propagation is exactly the period in which those stored copies expire and are gradually replaced with the new address.

How long DNS propagation actually takes

In practice, most visitors see the new site within minutes to a few hours. The official window you read about everywhere is 24-48 hours, but that covers the extreme cases, not the usual rule. So when someone promises “instant propagation,” they are really talking about a smartly set TTL, not magic.

The role of TTL in the whole story

The decisive factor is called TTL (Time To Live) — the number of seconds a server is allowed to keep the answer in cache. A TTL of 3600 means that, in the worst case, a resolver will keep serving the old address for one more hour after the change. A TTL of 300 means five minutes at most. In practice, you control the length of propagation through this single value.

Why delays happen

It is rarely your site’s fault. Most of the time, delays come from the way the DNS system is built globally. Here are the most common causes:

• A high TTL set before the move — caches hold on to the old address longer.
• ISP-level caching — some providers ignore the TTL and keep the answer longer than they should.
• Local cache, in your browser or operating system — you see the old site, even though the rest of the world already sees the new one.
• Changing the nameservers, not just the A record — this also involves the TLD zone and generally takes longer.
• Uneven propagation — DNS does not update everywhere at once, but server by server, region by region.

How to shorten propagation before the move

The most effective move is the one you make before touching anything. One or two days before migrating your WordPress site, lower the TTL to 300 seconds. That way, on moving day, caches expire quickly and the switch becomes almost instant for most visitors.

The rest of the plan is simple:

• Do the move when traffic is lowest — at night or at the start of the week.
• Test from several networks, not just from your home connection.
• Flush your local DNS cache if you still see the old version after a few hours.

If you are not sure how your domain is configured right now, a free audit shows you the current DNS settings and what risks exist before you press the button. For technical detail on how domain resolution works, the Google Public DNS documentation clearly explains the mechanism behind it.

How to check whether propagation is done

You do not have to guess. There are a few simple steps to find out whether the new address has reached you and the rest of the world:

• Use a “DNS checker” tool that queries servers in several countries at once.
• From the terminal, a command like nslookup or dig shows exactly which IP you are getting now.
• Open the site on mobile data, not just on Wi-Fi — it is a completely different network with a different cache.

If every source already shows you the new IP, propagation is finished for practically everyone. If you see mixed results, you just have a little more waiting to do — nothing to fix, only patience.

What visitors see during propagation

Here is the reassuring part: if you prepared the move correctly, almost no one sees a “broken” site. Some still land on the old server, others already on the new one — and both work, as long as you kept the old hosting active until propagation finishes.

That is why the golden rule is to never delete the old hosting right after the move. Keep it running for at least 48 hours. During that window, wherever a visitor lands, they will see a working site, and you avoid lost form submissions or orders that go nowhere.

In short, DNS propagation is not a bug but a normal, predictable, and controllable process. If you lower the TTL in advance, move during low-traffic hours, and keep the old server active for two days, the question “how long does it take” stops being a source of stress entirely.