You changed your nameservers or DNS records, and now the site opens for your friend but not for you — or shows the old page on mobile data and the new one on Wi-Fi. Nothing is broken: that's DNS propagation, and this article explains what it is and how to check it.
What propagation actually is
There is no single "update button" for the whole internet. Thousands of networks (your ISP, mobile carrier, office network) keep their own cached copies of DNS records, each with an expiry time (the record's TTL). When you change a record, each network keeps using its old copy until its cache expires — then it fetches the new one. That spreading process is propagation.
How long it takes (realistic ranges)
| Editing a DNS record (nameservers already here) | Minutes to a few hours for most visitors; up to the old record's TTL in the worst case |
| Changing nameservers | Typically 4–24 hours; occasionally up to 48 hours for the last caches worldwide |
| Brand-new domain | Often under an hour — there was no old cache anywhere |
How to check
- Use a public DNS checker (for example dnschecker.org): enter your domain, choose the record type (NS for nameservers, A for the website) and see what servers around the world currently answer. Green ticks with the new values = propagation is reaching those places.
- Test on a different network — switch your phone between Wi-Fi and mobile data. Different networks update at different speeds.
- Open the site in a private/incognito window so your browser's own cache doesn't fool you.
You cannot speed propagation up — no host can; it's how DNS works worldwide. What you CAN do next time: lower the TTL on records a day before a planned change, so caches expire faster when the change comes.
⚠ Common mistakes & fixes
- Re-editing records again and again while waiting: every change restarts caches in some places and makes results MORE confusing. Make the correct change once, then wait.
- Declaring "it's broken" after 30 minutes: after a nameserver change, give it at least several hours before troubleshooting — and check the DNS checker first.
- After 48 hours it still shows the old site everywhere: now something IS wrong — usually a typo in the nameservers or a record pointing at the old server. Re-check the values, then open a support ticket.
Related articles
- How to Point Your Domain to ZedgeHost (Nameservers)
- Fix: Domain Connected but Website Not Opening
- How to Manage DNS Records in cPanel (A, CNAME, TXT, MX)