Why your website sometimes takes hours (or days) to appear after changing DNS—and what you can do about it.
When you point your domain to a new hosting provider, you’re essentially telling the internet: “Hey, when someone types mydomain.com, send them to this server instead.” But here’s the catch—your computer doesn’t know this change happened overnight. It still remembers the old address.
DNS propagation is the process of your domain’s new information spreading from the root DNS servers down to all the intermediate servers that handle internet traffic. Think of it like updating a phone book for an entire country—it’s not instant, and different regions get the update at different times.
| Time Frame | What Happens | Percentage Propagated |
|---|---|---|
| 0-2 hours | Initial propagation begins | ~30% |
| 2-4 hours | Fastest propagation window | ~60-70% |
| 4-12 hours | Most servers updated | ~85-90% |
| 12-24 hours | Almost complete | ~95%+ |
| 24-48 hours | Full global propagation | 99.9%+ |
Every DNS record has a “Time To Live” setting that tells servers how long to cache it before checking for updates. Old-school DNS records often have 24-48 hour TTLs, meaning servers won’t check for changes until that timer expires.
DNS servers around the world don’t update simultaneously. A server in Tokyo might get the update before one in São Paulo simply due to how DNS propagation works.
Your Internet Service Provider (ISP) caches DNS records for their entire network. Even if your computer has the new IP, their servers might still serve the old one.
Before panicking that something went wrong, use these tools to verify propagation status:
💡 Pro tip: If you’re making DNS changes for a site already on Cloudflare, log into your Cloudflare dashboard and enable “Development Mode” to bypass caching during the transition.
If you know you’re switching hosts, lower your DNS TTL values 24-48 hours before the migration. Most hosting providers recommend setting TTL to 300-600 seconds (5-10 minutes) before making changes.
PapaBearHosting uses Anycast DNS with ultra-low 60-second TTL defaults. Our global network means your DNS changes typically propagate within seconds—not hours. Combined with our built-in CDN, your site stays fast everywhere.
Your local computer or ISP might still have the old DNS cached. Try clearing your browser cache, flushing your local DNS (Windows: ipconfig /flushdns, Mac: sudo dscacheutil -flushcache), or using a different network.
If your mail server stays the same (MX records unchanged), email continues working. If you’re switching email hosting too, set up the new mail server BEFORE changing MX records to avoid interruptions.
Some corporate networks and ISPs have aggressive DNS caching that exceeds standard TTLs. This is rare but can happen. Those users will see the new site once their ISP updates their cache.
Not completely—you can’t force other servers to update. However, using a DNS service with low TTL and ensuring your previous host hasn’t set excessively high cache times will make propagation as fast as possible.
Visitors might see a “site not found” error or be directed to the old host. Keep both sites running during the transition period to avoid downtime.
DNS propagation isn’t magic—it’s just the time it takes for the internet to agree on where your site lives. Most changes complete within 4 hours, and almost all complete within 48 hours.
With PapaBear’s Anycast DNS network, you’ll see the fastest propagation in the industry. Ready to make the switch? We’ll walk you through every step.
