Quick answer
DNS propagation usually takes from a few minutes to 48 hours, depending on the TTL value and caching at the provider. To speed it up, lower the TTL to 300 seconds before the change, clear the cache on your computer, and check records from multiple locations. If the change is not visible even after 48 hours, check that the zone is saved correctly and that the nameservers are updated.
How to recognize the problem
- The site opens on the old IP address or old hosting
- The new DNS change is not visible on your computer, but others can see it
- Emails are still going to the old server
- DNS checking tools show different results
- After changing nameservers, the site does not work or the old page opens
Most common causes
DNS record caching (TTL)
Every DNS record has a TTL (Time To Live) that determines how long it is cached by providers and devices. If the TTL was high (e.g., 86400 seconds), the change will not be visible until that period expires.
Insufficient waiting time for propagation
Changes are not applied instantly everywhere. Propagation can take up to 48 hours, although it is usually done within a few hours.
Error in DNS records
If the new A record is wrong, if a dot is missing at the end of the name, or if the record type is wrong, the change will not be visible or the site will stop working.
Nameservers not updated
When changing hosting, you need to update the nameservers at the registrar. If this is not done or done with an error, the old DNS still applies.
Local DNS cache
Your computer, router, or provider may hold old records in the cache. Sometimes it is enough to clear the cache to see the change.
Step-by-step fix
- 1
Check current DNS records
Use a tool like
nslookupor an online service (e.g.,dnschecker.org) to see which records are currently returned. Compare with what you set. Pay attention to the TTL value. - 2
Lower TTL before the change
If you plan a change, lower the TTL to 300 seconds (5 minutes) in the DNS panel early enough, at least as long as the old TTL (often 24 hours). Wait for the old TTL to expire, then enter the new value. This will shorten the propagation time.
- 3
Clear local DNS cache
On Windows, open Command Prompt as administrator and run
ipconfig /flushdns. On macOS, in Terminal typesudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder. On the router, restart the device or clear the cache if available. - 4
Check records from multiple locations
Use a tool like
dnschecker.orgorwhatsmydns.netto see if the new records are visible globally. If the new value is visible in most locations, propagation is complete. - 5
Check if nameservers are correct
In the registrar panel, check if the nameservers you set are correct and if they have propagated. You can use
whoisor an online tool to check nameservers. If not, wait or contact the registrar. - 6
Test from another device or network
Try accessing the site from mobile internet (turn off Wi-Fi) or via VPN. If the new page is visible there, the problem is in your network's cache.
- 7
Use public DNS servers
Temporarily configure your computer to use public DNS servers (e.g., Google 8.8.8.8 or Cloudflare 1.1.1.1). This can bypass your provider's cache. Change in network adapter settings, and after testing, revert to previous settings.
- 8
Wait and monitor propagation
If the records are correct, all that remains is to wait. Propagation usually takes up to 48 hours. Monitor the checking tools and note when the change appears.
If the change is not visible even after 48 hours
Check if you saved the change in the DNS panel and if the zone is active. Sometimes you need to click the button to apply changes. If you use a hosting provider, check if their nameservers are correct. Contact registrar or hosting support if you suspect an error. For advanced users: use the dig command from different public DNS servers to see if the records differ. For example, dig @8.8.8.8 yourdomain.com. If the results differ, propagation is still ongoing. Also, check if there is a DNSSEC error that can block changes.
How to prevent it
- Before any change, lower the TTL to 300 seconds and wait for the old one to expire.
- Keep records of DNS records and changes.
- Use a propagation checking tool before and after the change.
- Avoid changes on Friday or before the weekend.
When to call a professional
If you have checked the records, lowered the TTL, and cleared the cache, and the change is not visible even after 48 hours, or if you are not sure how to correctly set up DNS records, contact IT support. They can check the zone, nameservers, and any errors that prevent propagation.
Website development · Fast, SEO-ready, multilingual websitesFAQ
How long exactly does DNS propagation take?
Usually from a few minutes to 48 hours, depending on the TTL value and caching at the provider. If the TTL was low, the change is visible faster.
Why do I see the old page, but others see the new one?
Your computer or provider has probably cached the old DNS record. Clear the local DNS cache and try from another device or network.
Can I speed up propagation?
You cannot directly speed up propagation, but you can lower the TTL before the change and clear the cache on your devices. Using public DNS servers can help bypass the provider's cache.