What is DNS propagation?
When you change a DNS record — pointing your domain to a new host, or moving email — the change is instant at your DNS provider. But resolvers around the world keep the old answer until its TTL (time to live) runs out, so for a while some visitors reach the old server and some the new one. That gradual spread is called propagation.
How to check a change
- Enter the domain and the record type you changed: A for a website’s server, MX for email, NS for a change of DNS provider.
- Add the new value you expect, such as the new IP address, to see at a glance which resolvers have it.
- Check again later — each resolver updates when its cached answer expires.
How long does it take?
- Usually minutes to a few hours. It depends on the old record’s TTL: with a TTL of 3600, resolvers can keep the old answer for up to an hour.
- Changing name servers (NS) takes longest, often up to 24–48 hours, because the TTL is set by the registry and tends to be long.
- Lower the TTL a day before a planned move, then the change spreads in minutes.
Frequently asked questions
Why do resolvers show different IP addresses for big sites?
Large sites and CDNs answer with the server nearest to each resolver, so different answers are normal for them and do not mean a change is still spreading.
My site still shows the old version — what can I do?
Clear your browser cache, flush your computer’s DNS cache (ipconfig /flushdns on Windows) or switch to a resolver that already has the new record, such as 1.1.1.1.
Can I speed up DNS propagation?
Not for answers already cached. Lowering the TTL in advance is the only way to make the next change spread faster.