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 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.
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:
| Record | What It Does | Example Use |
|---|---|---|
| A record | Points a domain to an IPv4 address | Connecting your domain to your hosting server |
| AAAA record | Points a domain to an IPv6 address | Same job as an A record for newer IP addresses |
| CNAME | Points one name to another name | Making www point to your main domain |
| MX record | Tells the world where to deliver your email | Business email hosting |
| TXT record | Stores text used for verification and security | SPF, DKIM, Google Search Console verification |
| NS record | Names the servers in charge of your domain’s DNS | Switching your domain to a new host’s nameservers |
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.
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:
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.
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 Value | Equals | Best For |
|---|---|---|
| 300 | 5 minutes | Right before and during a migration |
| 3600 | 1 hour | Most everyday websites |
| 14400 | 4 hours | Common hosting default |
| 86400 | 24 hours | Stable 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.
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 Change | Typical Time | Why |
|---|---|---|
| A, AAAA or CNAME record edit | Minutes to a few hours | Depends on the record’s existing TTL |
| MX record (email) change | A few hours | Email servers also cache records |
| TXT record for verification | Minutes to an hour | Usually low TTL, quick lookups |
| Nameserver change | 24 to 48 hours | The .com registry commonly sets nameserver records with a 48 hour TTL |
| Brand new domain registration | Often under an hour, sometimes longer | No 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.
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 Change | Nameserver Change | |
|---|---|---|
| What moves | Just the record you edit | Every DNS record for the domain |
| Speed | Usually faster | Slower, up to 48 hours |
| Email risk | Low, MX records stay put | Higher if MX records aren’t recreated |
| Best for | Moving only the website | Moving 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.
Use a global DNS checker to see what resolvers in different locations return for your domain.
nslookup yourdomain.com 8.8.8.8 to ask Google Public DNS directly, or swap in 1.1.1.1 for Cloudflare.A mixed result is completely normal during propagation. Some locations will show the new IP while others still show the old one.
You can’t force the entire internet to refresh, but you can control the parts that are within reach.
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.
Often the internet has already updated and only your device is behind. Clear your local cache:
ipconfig /flushdnssudo dscacheutil -flushcache; sudo killall -HUP mDNSResponderresolvectl flush-cacheschrome://net-internals/#dns and clear the host cacheRestarting your router can also clear a cached answer stored there.
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.
Switch your phone from WiFi to mobile data. A different network often uses a different resolver, which gives you a quick second opinion.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.