You changed your nameservers or DNS records, but your website still shows the old content or an error. That delay is called DNS propagation.
How long does it take?
Often it takes from a few minutes to a few hours. Sometimes it can take up to 24-48 hours for the whole internet to see the change.
Why does it take time?
DNS information is cached by internet providers and devices to make browsing faster. Each cache keeps old data for a period set by the TTL (time to live). Until a cache expires, it can keep serving old information.
What affects the time?
- TTL value of the old record
- Your internet provider's caching
- The type of change (nameserver changes are usually slower than A record changes)
- Your own browser and device cache
How to check propagation
Use an online DNS checker to see what different locations return for your domain. You can also test the site from mobile data instead of Wi-Fi.
How to speed it up
- Before a planned change, lower the TTL to a small value a day earlier.
- Clear your browser cache.
- Flush your computer's DNS cache.
- Restart your router.
- Make sure the records are correct. Typos are the most common cause of "propagation problems".
Related guides
Read how to point a domain to hosting and how to migrate WordPress without downtime.
What DNS actually does
DNS works like the internet's phone book. It translates a name such as yourbrand.com into an IP address that computers can connect to. DNS records are stored on authoritative nameservers, and a chain of resolvers (your ISP, your router and your device) cache the answers for performance. "Propagation" is simply the time it takes for those caches to expire and fetch the new answer.
Common DNS records and how fast they change
| Record | Purpose |
|---|---|
| A | Points a name to an IPv4 address |
| AAAA | Points a name to an IPv6 address |
| CNAME | Alias from one name to another |
| MX | Tells the internet where to deliver email |
| TXT | Verification, SPF and DKIM settings |
| NS | Declares which nameservers control the domain |
A records usually update as fast as their TTL (for example 300 to 3600 seconds). NS changes can take longer because they involve the registry as well.
A safe plan for a website move
- Two days before: lower the TTL on existing records to something small like 300 seconds.
- Prepare and test the new server completely.
- On the day: make the DNS change.
- Keep the old server running for at least 48 hours in case some visitors still reach it.
- Raise the TTL back to a normal value once all is stable.
When it is not propagation
If the site is still wrong after 48 hours, the cause is almost always something else: wrong record values, the domain not added on the hosting account, an expired domain, or a registrar-level lock or parking. Check each of these, then contact support with the domain name and what you changed.
FAQ
Will my website go down during propagation?
Not if you migrate carefully. Keep the old site running until the new one works.
Ready to launch? Compare SyllHost hosting plans, or search for your domain on our domain search page. Questions? Talk to our team.