Domain Propagation

Domain propagation is the process of propagating changes to DNS to all servers in the world after you make changes to your domain settings — such as changing nameservers, updating A Records, or moving hosting.

During this process, some visitors may still see the old version of your website, while others will see the new version.

Simple analogy

Imagine you move your office to a new address and update the information in Google Maps. Not everyone immediately sees the new address at the same time — some have had their apps updated, some haven't. During that period, some people were still directed to the old address.

Domain propagation works exactly like that, but scales to thousands of DNS servers around the world.

Why Does Propagation Take Time?

Every DNS server in the world stores a local copy of domain data called a cache. This cache is not updated in real-time — instead based on the TTL (Time to Live) value you specify in your DNS settings.

T

T

L is an instruction to the DNS server: "keep this data for X seconds, then re-request it from the original source."

If your TTL is set to 86,400 seconds (24 hours), it means that DNS servers around the world can store old data for up to 24 hours before updating it — even if you have changed the settings on your end.

How Long Does Propagation Take?

How to Monitor Propagation Status

You don't have to wait in blindness. The following tools allow you to see whether DNS changes have spread to various locations in the world:

• WhatsMyDNS.net — Check propagation from dozens of locations at once
• DNSChecker.org — Visual display of propagation status per country
• MXToolbox — Specifically for verifying MX Records and configuration SMTP

How to Speed Up Propagation

Propagation cannot be forced to complete instantly, but there are several things you can do to minimize waiting time:

• Lower TTL before making changes — Ideally 24–48 hours before migration, set TTL to a low value such as 300 seconds (5 minutes). Once propagation is complete, increase it back to the normal value.

• Use nameservers with fast propagation — Some DNS providers such as Cloudflare are known to have faster propagation times than the registrar's default nameservers.

• Flush DNS cache on your device — After changes are made, flush the local DNS cache so your browser doesn't continue reading old data.

• Try access via a different network — Switching from WiFi to cellular data (or vice versa) can indicate whether propagation has completed on a particular ISP.

To flush DNS cache in Windows, run the following command in Command Prompt:

ipconfig /flushdns

On mac

OS:

sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder

What You Need to Pay Attention to

• Do not change nameservers twice in a row — Each nameserver change restarts the propagation process from the beginning. Wait until the first propagation is complete before making the next change.
• Email may be affected during propagation — If you move hosting at once, there is a risk that incoming email will not be delivered as long as the MX Record has not been fully propagated. Coordinate DNS changes on an appropriate schedule.
• CDN has its own cache layer — If your domain uses a CDN, DNS changes also need to be followed by a cache purge on the CDN so that the new content is served correctly.
• IP Address new server must be active — Make sure the destination server is running and accessible before you point DNS to it. Completed propagation to a server that is not ready is tantamount to downtime.

FAQs