DNS propagation is the time it takes for a change to your domain’s DNS records to update across the internet. Because DNS servers worldwide store cached copies of your records, some visitors see the new version while others still see the old one. Most updates finish within a few hours, but nameserver changes can take up to 48 hours.
You moved your website to a new host, updated your domain settings, and refreshed the page. The old site is still there. Your colleague in another state sees the new one. Your phone shows something else entirely.
Nothing is broken. You are watching DNS propagation happen in real time.
This guide explains what DNS propagation is, why it takes time, how to check its progress, and the practical steps that make the next migration, domain connection, or email change far smoother. You will also learn the one setting most people forget to adjust before making a change, which is the single biggest factor in how long you wait.
DNS (Domain Name System) is the internet’s address book. It translates a human friendly domain name like webhostservers.co into the numeric IP address of the server where the website actually lives.
When someone types your domain into a browser, their device asks a DNS resolver (usually run by their internet provider, or a public service like Google Public DNS or Cloudflare’s 1.1.1.1) where to find it. The resolver looks up the answer, hands it back, and the browser connects to the correct server.
This lookup happens in milliseconds, and it happens billions of times a day. To keep the internet fast, resolvers save the answers they find. That saving step, called caching, is exactly why changes do not appear instantly.
DNS propagation is the period between updating a DNS record and every resolver in the world replacing its saved copy with the new information.
The word “propagation” is a little misleading. Your change is not slowly traveling from server to server. Your authoritative DNS server updates almost immediately. What takes time is waiting for thousands of independent resolvers to notice their saved copy has expired and request a fresh one.
Think of it like changing your mailing address. The post office has your new address right away, but friends who wrote down the old one keep using it until they check again.
Most DNS record changes update within 1 to 4 hours, while nameserver changes can take 24 to 48 hours to finish everywhere. The exact time depends on the TTL value of the record and how each resolver handles caching.
| Type of change | Typical time to update | Why |
|---|---|---|
| A record (pointing domain to a new server IP) | Minutes to a few hours | Controlled by your record’s TTL |
| CNAME record (alias such as www) | Minutes to a few hours | Controlled by your record’s TTL |
| MX record (email routing) | Minutes to a few hours | Controlled by your record’s TTL |
| TXT record (SPF, verification codes) | Minutes to a few hours | Controlled by your record’s TTL |
| Nameserver change at your registrar | Up to 24 to 48 hours | The registry for the domain extension sets a long cache time on nameserver records |
| Brand new domain registration | Often under an hour, occasionally longer | Resolvers have no old copy to forget |
The 48 hour figure exists for a real reason. For .com domains, the registry publishes nameserver records with a TTL of 172,800 seconds, which equals exactly 48 hours. A resolver that cached your old nameservers just before you changed them can legally keep using them for that long.
TTL (Time to Live) is a number, measured in seconds, attached to every DNS record that tells resolvers how long they may keep a cached copy before asking again.
Common TTL values you will see in a DNS editor:
Here is the part most website owners miss. The TTL that matters is the old one, not the new one. If your A record had a TTL of 86400 when you changed it, some visitors may see the old server for up to a full day, even if you set the new record to 300.
Imagine a bakery owner in Austin moving her site to a new host on Friday morning. Her A record has a TTL of 14400 (4 hours).
Same change, very different weekend.
You can check DNS propagation with an online global checker, a command line lookup, or by querying a specific public resolver directly. Each method shows what a different part of the internet currently sees for your domain.
Tools like whatsmydns.net and DNSChecker.org query resolvers in dozens of cities worldwide, including New York, Dallas, Los Angeles, and Chicago. Enter your domain, choose the record type (A, MX, CNAME, TXT, or NS), and you will see a map showing which locations return the new value.
Green checkmarks across the board mean propagation is essentially done.
nslookup yourdomain.comdig yourdomain.comTo ask a specific public resolver, add its address. For example, nslookup yourdomain.com 8.8.8.8 asks Google Public DNS, and nslookup yourdomain.com 1.1.1.1 asks Cloudflare.
If an online checker shows your new IP when querying your authoritative nameservers, your change is live at the source. Anything still showing the old value is simply a cache waiting to expire.
You cannot force the whole internet to update, but you can shorten the wait and refresh what you personally see. Plan ahead with TTL, then clear the caches you control.
ipconfig /flushdns in Command Prompt. On a Mac, Apple’s support documentation lists the Terminal command for your macOS version. In Chrome, visit chrome://net-internals/#dns and click “Clear host cache.”Changing nameservers moves control of your entire DNS zone to a new provider, while changing a DNS record edits one entry inside the zone you already use.
| Changing Nameservers | Changing Individual DNS Records | |
|---|---|---|
| Where you do it | Domain registrar | DNS zone editor (host, registrar, or DNS provider) |
| What it affects | Every record: website, email, subdomains | Only the record you edit |
| Typical wait | Up to 48 hours | Usually minutes to hours, based on TTL |
| Risk level | Higher; missing records break email or subdomains | Lower; changes are isolated |
| Best for | Moving everything to a new host or DNS provider | Pointing a site to a new IP, adding email, verifying services |
Our recommendation: if your only goal is pointing a website to a new server, editing the A record is usually faster and lower risk than switching nameservers. Switching nameservers makes more sense when you want one provider to manage everything going forward.
Most “propagation problems” are actually configuration mistakes. These are the ones we see most often:
DNS is simple once it is set up correctly, but a mistake can take a website or business email offline. Consider asking your hosting provider’s support team for help when:
A good host can review your zone, spot missing records, and often handle the migration so the switch happens with little or no visible downtime.
nslookup and dig.You and your friend are likely using different DNS resolvers. Each resolver caches records independently, so one may already have your new IP address while the other is still holding the old one until its TTL expires. Clearing your local DNS cache or checking from another network usually reveals the updated site.
You cannot force every resolver to refresh, but you can shorten the wait. Lower the TTL on the records you plan to change to 300 seconds a day or two in advance. After the change, flush your local cache and use the free purge tools from Google Public DNS and Cloudflare.
Yes. If you change MX records or switch nameservers, some mail servers may deliver to the old destination until their cache expires. Keeping the old mailbox active for a few days and confirming that every MX and SPF record was copied correctly prevents lost messages during the transition.
Usually not, as long as both the old and new servers are running. Visitors are simply directed to whichever server their resolver currently knows about. Downtime typically happens only when the old hosting is cancelled too soon or a record on the new server is missing.
For normal day to day operation, 3600 seconds (1 hour) is a sensible balance between speed and efficiency. Drop it to 300 seconds before planned changes, then raise it again once everything is stable. Very long TTLs make future changes slower to roll out.
Nameserver records are cached at the registry level for the domain extension, and those records carry long TTLs. For .com domains, that TTL is 172,800 seconds, which is exactly 48 hours. Many resolvers refresh sooner, but the full window can last that long.
Run your domain through a global checker such as whatsmydns.net. When locations across the United States and other regions all return your new IP address or nameservers, propagation is effectively complete. You can also run nslookup against several public resolvers to confirm consistent results.
In most cases, yes. Certificate authorities like Let’s Encrypt confirm you control the domain by checking that it points to your server or contains a specific DNS record. Until DNS resolves to the new host, that verification can fail, so install SSL after the domain points to the right place.
DNS propagation is not a glitch. It is the internet’s caching system doing its job, keeping lookups fast for billions of visitors every day. Once you understand that TTL sets the pace, the process becomes predictable: lower the TTL ahead of time, make your change during quiet hours, keep the old server running, and confirm with a global checker.
Planning a move or connecting a new domain and want an extra set of eyes on your DNS settings? The team at Web Host Servers offers free website migration and real human support around the clock, so you can make the switch with confidence. Reach out anytime at +1 (213) 293 0540 or info@webhostservers.co.