Skip to main content

Web Host Servers

DNS Propagation Explained: Why Your New Website Isn’t Showing Up Yet

DNS propagation is the time it takes for a change to your domain’s DNS records to spread across internet servers worldwide. Most record changes show up within a few hours, while nameserver changes can take up to 48 hours. The delay happens because servers keep cached copies of old records until their TTL expires.

You Changed Your Domain Settings. So Why Is the Old Site Still Loading?

You just pointed your domain to a new host, hit save, and opened your website. Nothing changed. Maybe you see the old site, a blank page, or a “site can’t be reached” error. Then your friend in another state says the new site loads perfectly for them.

Nothing is broken. You’re watching DNS propagation happen in real time.

This guide explains what’s actually going on behind the scenes, how long you should realistically wait, how to check progress, and the simple steps that make your next domain change or hosting move much smoother.

What Is DNS and Why Does It Matter?

DNS (Domain Name System) is the internet’s address book. It translates a human friendly name like webhostservers.co into the numeric IP address of the server where the website lives.

Every time someone types your domain, their device asks a DNS resolver, “Where does this domain live?” The resolver finds the answer, hands back an IP address, and the browser connects to that server.

The key records you’ll run into include:

RecordWhat It DoesExample Use
A recordPoints a domain to an IPv4 addressConnecting your domain to your hosting server
AAAA recordPoints a domain to an IPv6 addressSame job as an A record for newer IP addresses
CNAMEPoints one name to another nameMaking www point to your main domain
MX recordTells the world where to deliver your emailBusiness email hosting
TXT recordStores text used for verification and securitySPF, DKIM, Google Search Console verification
NS recordNames the servers in charge of your domain’s DNSSwitching your domain to a new host’s nameservers

What Exactly Is DNS Propagation?

DNS propagation is the window between saving a DNS change and every resolver on the internet seeing that change.

The word “propagation” is a little misleading. Your update doesn’t actively travel across the internet. Instead, thousands of DNS resolvers run by internet providers, companies, and public services like Google Public DNS and Cloudflare’s 1.1.1.1 each keep a cached copy of your old record. They only ask for a fresh copy once their saved version expires.

So propagation is really a waiting game. Different resolvers refreshed at different times, which is why your site can look updated in one city and outdated in another.

Why Does DNS Propagation Take So Long?

Caching is the main reason. DNS records are stored at several layers, and each layer holds on to the old answer until it expires.

Here’s where old information can hide:

  1. Your browser keeps its own short DNS cache.
  2. Your computer or phone caches DNS lookups at the operating system level.
  3. Your router may cache lookups for everyone on your network.
  4. Your internet provider’s resolver caches answers for all its customers.
  5. The top level domain registry (such as the .com registry) caches nameserver information when you switch nameservers.

This caching is a feature, not a flaw. Without it, every single page visit would trigger a full lookup chain, making the web slower and putting enormous load on DNS servers.

What Is TTL and How Does It Control Propagation?

TTL (time to live) is a number, measured in seconds, that tells resolvers how long they can keep a DNS record before checking for a new one.

If your A record has a TTL of 3600, resolvers may serve the cached answer for up to one hour. After that, they ask again and pick up your change.

TTL ValueEqualsBest For
3005 minutesRight before and during a migration
36001 hourMost everyday websites
144004 hoursCommon hosting default
8640024 hoursStable records that rarely change

A practical way to think about it: your worst case wait for a simple record change is roughly the TTL that was in place before you made the change. Lowering the TTL after the edit doesn’t help much, because resolvers already cached the old record with the old timer.

How Long Does DNS Propagation Take?

Most A record and CNAME changes appear within a few minutes to a few hours. Nameserver changes usually finish within 24 hours but can take up to 48 hours.

Type of ChangeTypical TimeWhy
A, AAAA or CNAME record editMinutes to a few hoursDepends on the record’s existing TTL
MX record (email) changeA few hoursEmail servers also cache records
TXT record for verificationMinutes to an hourUsually low TTL, quick lookups
Nameserver change24 to 48 hoursThe .com registry commonly sets nameserver records with a 48 hour TTL
Brand new domain registrationOften under an hour, sometimes longerNo old cache exists yet

The 48 hour figure you see everywhere comes from nameserver changes. For .com domains, the registry’s nameserver records commonly carry a TTL of 172,800 seconds, which is exactly 48 hours. In practice, many visitors see the change much sooner.

Nameserver Change vs A Record Change: Which Should You Use?

An A record change is faster and safer when you only want to move your website. A nameserver change moves control of your entire DNS zone to a new provider.

 A Record ChangeNameserver Change
What movesJust the record you editEvery DNS record for the domain
SpeedUsually fasterSlower, up to 48 hours
Email riskLow, MX records stay putHigher if MX records aren’t recreated
Best forMoving only the websiteMoving everything to a new host

Our take: if your email lives somewhere else, such as Google Workspace or Microsoft 365, and you only want your website on a new server, changing the A record is usually the smoother path. If you want your host to manage everything in one control panel, switching nameservers makes sense, as long as you copy every existing record first.

How to Check DNS Propagation

Use a global DNS checker to see what resolvers in different locations return for your domain.

  1. Use an online propagation checker. Tools like WhatsMyDNS.net or DNSChecker.org query servers around the world and show which IP address each one returns. Green checks with your new IP mean that location sees the update.
  2. Query a specific resolver. On a computer, run nslookup yourdomain.com 8.8.8.8 to ask Google Public DNS directly, or swap in 1.1.1.1 for Cloudflare.
  3. Compare against your host’s IP. Find your server’s IP in your hosting control panel and confirm the checker shows the same address.
  4. Check the right record type. If email is the issue, check MX records, not A records.

A mixed result is completely normal during propagation. Some locations will show the new IP while others still show the old one.

How to Speed Up DNS Propagation

You can’t force the entire internet to refresh, but you can control the parts that are within reach.

Plan Ahead by Lowering Your TTL

The single most effective move is lowering your TTL to 300 seconds at least 24 to 48 hours before a planned change. That gives the old, longer TTL time to expire everywhere. When you finally switch, resolvers pick up the new record within minutes.

Clear Your Own DNS Cache

Often the internet has already updated and only your device is behind. Clear your local cache:

  • Windows: open Command Prompt and run ipconfig /flushdns
  • macOS: open Terminal and run sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder
  • Linux (systemd): run resolvectl flush-caches
  • Google Chrome: visit chrome://net-internals/#dns and clear the host cache

Restarting your router can also clear a cached answer stored there.

Ask Public Resolvers to Refresh

Google Public DNS and Cloudflare both offer free cache purge pages where you can request a refresh for your domain. This helps visitors who use those resolvers.

Test With a Different Network

Switch your phone from WiFi to mobile data. A different network often uses a different resolver, which gives you a quick second opinion.

A Real World Example: Moving a Small Business Site Without Downtime

Imagine a bakery owner in Austin moving her WordPress site to a new host on a Friday.

Wednesday: She lowers the A record TTL from 14400 (4 hours) to 300 (5 minutes).

Friday morning: Her new host copies the website files, database, and email accounts. She previews the site on the new server using a temporary URL to confirm everything works.

Friday afternoon: She updates the A record to the new server’s IP. Within about 15 minutes, most global checkers show the new address. She flushes her laptop’s DNS cache and sees the new site.

Saturday: She keeps the old hosting account active, just in case a few visitors still reach the old server. A week later, she raises the TTL back to 3600 and cancels the old plan.

Result: no downtime, no lost orders, and no panicked weekend. The difference was planning the TTL two days early and keeping both servers live during the overlap.

Common DNS Propagation Mistakes to Avoid

  • Canceling old hosting too early. Keep it running for at least 48 to 72 hours after the switch so visitors on slow resolvers still reach a working site.
  • Forgetting MX records when switching nameservers. This is the most common cause of “my email stopped working after I moved my website.”
  • Editing records at the wrong place. If your domain uses your host’s nameservers, edits made at your registrar won’t do anything. Always edit DNS wherever your nameservers point.
  • Making changes over and over. Each edit can restart caching. Make one correct change and give it time.
  • Expecting SSL to work instantly. Free SSL certificates, such as those from Let’s Encrypt, usually need the domain to point at the new server before they can be issued. A short security warning right after a move is normal.
  • Leaving the TTL at 300 forever. Very low TTLs mean more lookups. Raise it back to a normal value once things are stable.
  • Assuming a stale page means DNS failed. Your browser or a caching plugin may be showing an old copy. Try a private window first.

When Should You Get Professional Help?

If your site still isn’t loading after 48 hours, something other than propagation is usually the problem.

At that point, it’s worth contacting your hosting support team. Common culprits include a typo in the IP address, a conflicting duplicate A record, DNSSEC settings that don’t match the new provider, an expired domain, or a registrar lock. These are quick fixes for an experienced technician but frustrating to hunt down alone.

Key Takeaways

  • DNS propagation is the delay between saving a DNS change and every resolver worldwide seeing it.
  • Caching at the browser, device, router, ISP, and registry levels causes the delay.
  • TTL decides how long old records stay cached. Lower it to 300 seconds a day or two before any planned change.
  • Record changes often finish in minutes to hours. Nameserver changes can take up to 48 hours.
  • Use global checkers like WhatsMyDNS.net to track progress, and flush your local DNS cache to see changes faster.
  • Keep old hosting active for a few days after a move and always copy MX records when changing nameservers.
  • No progress after 48 hours usually signals a configuration issue, not slow propagation.

Frequently Asked Questions

What does DNS propagation mean?

DNS propagation is the period after you update a domain’s DNS records when servers across the internet still use cached older information. As each server’s cache expires based on the record’s TTL, it fetches the updated record. Once all servers refresh, your change is fully visible everywhere.

How long does DNS propagation take?

Simple record changes like an A record or CNAME typically take a few minutes to a few hours, depending on the TTL. Nameserver changes usually complete within 24 hours but can take up to 48 hours. Brand new domains often resolve within an hour because no old cached records exist yet.

Why can I see my new website but my customers can’t?

You and your customers likely use different DNS resolvers. Your resolver may have refreshed its cache already while theirs is still holding the old record. This is normal during propagation. Within the TTL window, most visitors will see the updated site without anyone needing to do anything.

Can I speed up DNS propagation?

You can’t force every server worldwide to refresh, but you can shorten the wait. Lower your TTL to 300 seconds a day or two before the change, flush your local DNS cache, request a cache refresh from Google Public DNS and Cloudflare, and avoid making repeated edits while changes spread.

Does DNS propagation affect email?

Yes, if your MX records change. During propagation, some email may still route to the old mail server. That’s why it helps to keep the old mailbox active for a few days. When switching nameservers, always recreate your MX, SPF, and DKIM records at the new provider first to avoid lost messages.

Is it safe to change DNS records on a live website?

Yes, when it’s planned. Lower the TTL in advance, confirm the new server is fully working, then make the change. Keep the old server running during the overlap so every visitor reaches a working site. Downtime usually comes from canceling old hosting too early or entering a wrong IP address.

What’s the difference between a domain registrar and a web host?

A domain registrar is where you buy and renew your domain name, such as Namecheap or GoDaddy. A web host stores your website’s files and serves them to visitors. DNS connects the two by telling browsers which hosting server your domain points to. Some companies offer both services.

What should I do if my site isn’t working after 48 hours?

Check that the IP address in your A record matches your hosting server exactly, look for duplicate or conflicting records, and confirm you’re editing DNS where your nameservers point. Also verify your domain hasn’t expired. If everything looks correct, contact your hosting support team for a hands on review.

Conclusion

DNS propagation can feel like your website has disappeared, but it’s simply the internet catching up. Once you understand caching and TTL, the waiting stops being a mystery and becomes something you can plan around.

The smoothest domain changes and hosting moves come down to a few habits: lower your TTL early, copy every record before switching nameservers, keep your old hosting live for a few days, and check progress with a global DNS tool instead of guessing.

If you’re planning a move and want a hand, the Web Host Servers team offers free website migration and real human support around the clock. Reach out to our team anytime and we’ll help you get your domain pointed the right way.