DNS propagation is the process by which DNS changes — such as pointing a domain to a new server — spread across all DNS servers on the internet. When you update your nameservers or any DNS record, the change does not take effect instantly worldwide. Depending on your TTL settings and your ISP’s caching behavior, it can take anywhere from a few minutes to 48 hours for everyone to see the updated version.
In this guide, you will learn exactly how DNS propagation works, why it takes time, how to speed it up, and how to check whether your changes have already propagated in different parts of the world.
Check DNS propagation now
See what 10 public DNS resolvers in different countries return for a record right now, and how long each will keep its cached answer. Add the new value you set to see which ones already have it.
Queries go from your browser to each resolver over DNS over HTTPS. Large resolvers answer from the server nearest to you, so the results show what these networks see from your region. Nothing you type is stored. Source: copahost.com
Table of Contents
DNS Propagation basics
When you change the nameservers of a domain, it can take 24 to 48 hours for the update to fully take effect.
This delay happens because internet providers around the world need time to refresh their systems. They’ll check and update the new DNS information for your domain. If it takes longer, we recommend this article about how to fix slow DNS lookups.
This process is called DNS propagation – it’s the time needed for all DNS servers across the internet to recognize the new location of your website.
Usually, it takes 1 to 2 days, but in some cases, it might be quicker or take a bit longer.
DNS Propagation time
The providers must update their DNS caches from time to time. They have to keep caches, in order not to overload the internet.
How long it takes depends on two numbers, not on how fast the internet is. The first is the TTL of the record you changed, which tells each resolver how long to keep its cached copy: with a TTL of 300 seconds, resolvers ask again within 5 minutes; with 86400, it can take a full day.
The second applies only when you change nameservers. The registry of your domain name’s extension publishes the delegation, the record that says which nameservers answer for your domain, with its own TTL. For .com and .net that TTL is 48 hours, and you can’t lower it.
Is it possible to speed up DNS propagation?
DNS propagation is largely automatic: each resolver keeps a cached record for as long as its TTL says.
When the cached copy expires, the resolver asks the domain’s authoritative nameservers again and gets whatever is there now. However, we can force our PC to look up again for the updated DNS. In Windows command prompt, this will flush your DNS cache:
ipconfig /flushdnsOr even, we can simply change our local DNS servers. Switching to a public DNS server gives your device a different resolver, which may already have the updated record. The checker at the top of this page shows which public resolvers already have it.
We can recommend these free DNS resolvers:
- Google DNS: 8.8.8.8 and 8.8.4.4
- Cloudflare: 1.1.1.1 and 1.0.0.1
- OpenDNS: 208.67.220.220 and 208.67.222.222
How does a DNS query work?
Simple explanation
Every network device on the web makes use of an IP address to route requests. This is similar to someone asking the DNS server what is the IP address of a certain domain.
Then, the DNS server answers this question, with the corresponding IP address. Whenever you type a URL and hit enter, your browser makes a request for a particular website.
This process is managed by your ISP — whether that is a cable provider, a DSL broadband provider, or a corporate network.
The DNS resolver for the ISP forwards the request for a particular website to a DNS root name server. And once the DNS server finds the IP address for the requested website, it will answer with the corresponding IP address.
Further, your local ISP will provide the host IP address to your browser.
Sometimes your ISP can’t find the IP address information locally. In this case, it forwards the query to other DNS servers in the world. The DNS servers will “talk” between them to fetch the IP address information of a domain.
Detailed explanation
The Domain Name System (DNS) resolution involves several entities working together: the client, the DNS resolver, and root name servers.
Here’s a step-by-step overview of the DNS communication process:
Client Initiates DNS Query. The process begins when a client, such as a web browser, initiates a DNS query. It requests the IP address corresponding to a domain name.
For example, the client wants to resolve the domain name “example.com” to an IP address. DNS works the same way, either for ipv6 or ipv4 addresses.
DNS Resolver Receives the Query. The DNS resolver, usually provided by the client’s ISP or network, receives the DNS query from the client. The resolver checks its local cache to see if it has the IP address for the requested domain name. There is a DNS hierarchy.
If the information has expired, or else if it’s not present in the cache, the DNS server resolves the query.
Recursive Query. The DNS resolver performs a recursive resolver query to find the IP address for the domain name.
It starts by querying the root DNS servers. Then it sends a request to the top-level domain (TLD) servers that handle the requested domain extension (.com, .net, etc.).
Then…
TLD Name Server Resolution. The root DNS servers respond to the resolver with the IP address of the appropriate TLD name server.
The one responsible for the requested domain extension (e.g., the .com TLD server). The resolver then queries the TLD name server.
Authoritative Name Server Resolution. The TLD name server responds to the resolver with the IP address of the authoritative name server. The one responsible for the specific domain (e.g., the authoritative name server for “example.com”). The resolver then queries the authoritative name server.
Response and Caching. The authoritative name server responds to the resolver with the requested IP address. The resolver caches this response and sends it back to the client. The client can now use the obtained IP address to establish a connection with the desired resource (e.g., a web server).
Throughout the process, the devices use UDP or TCP packets to exchange DNS messages. It depends on the specific query and response sizes.
This distributed design allows DNS to resolve millions of domain names across the internet efficiently.
Subsequent queries for the same domain are served from the resolver’s cache, skipping the full resolution process until the cached record expires.
How to Check DNS Propagation
After updating your DNS records, you will want to confirm whether the changes have propagated in different regions of the world. There are two main ways to do this: using an online tool or using the command line.
Using an online tool
The quickest way is the DNS propagation checker at the top of this page. Enter your domain and the record type, and it asks 10 public resolvers based in the United States, Canada, Europe, Japan and China what they return right now, along with how long each one will keep its cached answer. Add the new value in Expected value and it marks which resolvers already have it and which still return the old one.
MXToolbox Useful for checking MX records and diagnosing email delivery issues during or after a DNS migration. For the whole process, see our guide on email migration.
Using the command line
For a more technical check, you can query DNS records directly from your terminal:
On Linux or macOS:
dig copahost.com A
dig copahost.com NS
dig copahost.com MXOn Windows:
nslookup copahost.com
nslookup -type=MX copahost.com
nslookup -type=NS copahost.comTo check against a specific DNS server — for example, to see what Google’s DNS currently returns for your domain — use:
dig @8.8.8.8 copahost.com AThis is useful for comparing what different DNS resolvers around the world are currently seeing for your domain.
Why is DNS Propagation Taking So Long?
In most cases, DNS propagation completes within a few hours. But sometimes it takes longer than expected. Here are the most common reasons:
High TTL value TTL (Time to Live) is the main factor controlling propagation speed. If your TTL was set to a high value — such as 86400 seconds (24 hours) — before you made the DNS change, every DNS resolver on the internet will keep serving the old record for up to 24 hours before checking for updates. There is no way to override this retroactively.
ISP caching behavior Some Internet Service Providers ignore TTL values and cache DNS records for longer than they should. It’s outside your control.
DNS resolver cache not cleared Your own device or browser may still be serving a locally cached version of the old DNS record. Flushing your DNS cache (see commands in the previous section) can resolve this immediately for your own connection, without waiting for global propagation.
Incorrect DNS configuration If the new DNS records contain errors — such as a typo in an IP address or a missing trailing dot in a hostname — some resolvers may fail to resolve the record correctly, which can look like a propagation issue but is actually a configuration problem. Always double-check your records using a tool like MXToolbox before concluding that propagation is the issue.
Multiple layers of caching DNS queries pass through several layers — your browser, your operating system, your router, your ISP’s resolver, and upstream resolvers. Each layer has its own cache. Even after your ISP has updated its cache, your local device may still be serving the old result.
How to Reduce TTL Before a Migration
Reducing your TTL before a DNS migration is one of the most effective ways to speed up propagation when you need to move your website to a new server. Here is the recommended process:
Step 1: Lower your TTL well in advance
At least 48 hours before the planned migration, log in to your DNS management panel and reduce the TTL of the records you intend to change — typically the A record — to 300 seconds (5 minutes).
This gives existing caches time to expire and start using the shorter TTL. Once the 48-hour window has passed, most resolvers around the world will be refreshing your DNS record every 5 minutes instead of every 24 hours.
Step 2: Make the DNS change
When you are ready to migrate, update the DNS record (such as the A record) to point to the new server’s IP address. Because the TTL is now 300 seconds, most DNS resolvers will pick up the change within minutes rather than hours.
Step 3: Monitor propagation
Run the DNS propagation checker with your new IP in Expected value. Since the TTL is now 300 seconds, resolvers should switch within about 5 minutes, and the checker shows how long any resolver still behind will keep the old value.
Step 4: Restore the TTL
Once propagation is confirmed and the new server is stable, restore the TTL to a standard value such as 3600 seconds (1 hour) or 86400 seconds (24 hours). Keeping a very low TTL permanently increases the load on your DNS servers unnecessarily.
| Stage | Action | TTL Value |
|---|---|---|
| 48h before migration | Lower TTL | 300 seconds (5 min) |
| At migration | Update DNS record | 300 seconds (5 min) |
| After confirmation | Restore TTL | 3600–86400 seconds |
DNS Propagation by Record Type
All record types follow the same rule: a change reaches each resolver when its cached copy expires. The exception is a nameserver change, which depends on a TTL you don’t control. Here is what to expect for the most common record types:
A Record The most frequently updated record type, used when migrating a website to a new server. The wait equals the TTL that was in place before the change: up to 1 hour with a TTL of 3600 seconds, and about 5 minutes if you lowered it to 300 seconds in advance.
AAAA Record Behaves identically to the A record in terms of propagation. The only difference is that it maps to an IPv6 address (the AAAA record) instead of IPv4.
MX Record Used for email routing. MX records follow the same TTL rule. While resolvers still hold the old MX, some messages keep arriving at the old mail server, so keep the old mailboxes active for a few days after the switch and check them before closing the account.
NS Record Nameserver changes take the longest. The delegation that points your domain to its nameservers is published by the registry of the extension, not by your DNS provider, and for .com and .net it has a 48-hour TTL. Resolvers can keep the old nameservers for up to two days, whatever TTL you set at the new provider.
This is why a hosting move that includes a nameserver change involves the longest wait. Our website migration checklist covers how to sequence the change so the wait doesn’t become downtime.
CNAME Record Same rule as the A record: the TTL in place before the change sets the wait.
TXT Record Commonly updated for SPF, DKIM and domain verification purposes. Same rule as well. Receiving mail servers look up SPF, DKIM and DMARC when a message arrives, so a change counts as soon as their resolver’s cached copy expires.
| Record type | What sets the wait | With TTL 300 s | With TTL 3600 s |
|---|---|---|---|
| A, AAAA, CNAME | The record’s TTL | About 5 min | Up to 1 hour |
| MX | The record’s TTL | About 5 min | Up to 1 hour |
| TXT (SPF, DKIM, DMARC) | The record’s TTL | About 5 min | Up to 1 hour |
| NS (nameserver change) | The registry’s delegation TTL | Up to 48 hours on .com and .net | Up to 48 hours on .com and .net |
A record that didn’t exist before follows a different timer: resolvers that looked for it earlier cached the “no record” answer for the negative-cache time set in your zone’s SOA record. The checker above shows that remaining time too.
What does DNS Cache mean?
DNS cache (also known as DNS resolver cache) refers to a process of storing data temporarily. For example, data about the previous DNS lookups on the computer’s operating system or browser.
The DNS cache maintains a record (IP address) of all recently viewed websites and domains. Maintaining a cached copy of DNS lookups speeds up the process of data retrieval. Speeds up IP address resolution as well, by avoiding the need to go through the complete process of DNS lookup again.
How to verify the health of my DNS?
Once your DNS has fully propagated, it is good practice to run a quick check to make sure all your records are resolving correctly. You can use tools like nslookup or dig to perform a DNS lookup and confirm that the expected IP addresses and records are being returned.
For a complete walkthrough of DNS record types, how to check each one, and how to use diagnostic tools in detail, see our full guide: What does DNS stand for? How it works, types and examples
Frequently Asked Questions about DNS Propagation
Why is my DNS not propagating?
The most common reasons are a high TTL that was in place before the change, an edit made at a DNS provider your domain doesn’t use, or an error in the new records. The checker at the top of this page shows your domain’s nameservers, so you can confirm where the record has to be edited. If only your own computer still shows the old version, flush your local DNS cache.
Does DNS propagation affect email?
Yes, if you change your MX records. Until each resolver’s cached copy expires, some senders still deliver to the old mail server, for as long as the MX record’s TTL: up to 1 hour with a TTL of 3600 seconds. Keep the old mailboxes active for a few days after the switch and check them before closing the account.
Can I use my website during DNS propagation?
Yes, but the experience may be inconsistent. During propagation, some visitors reach the old server while others already reach the new one, depending on which DNS resolver they use. Keep both servers running and serving the same content until propagation is complete.
What is TTL in DNS propagation?
TTL (Time to Live) is a value set on each DNS record that tells resolvers how long to cache it before asking again. A TTL of 3600 means resolvers keep the record for 1 hour. A lower TTL makes changes reach everyone faster, while a higher one reduces the number of queries to your nameservers. Lowering the TTL to 300 seconds before a planned migration is the most effective way to shorten the wait.
How do I know when DNS propagation is complete?
Run the DNS propagation checker at the top of this page with the new value in Expected value. It asks 10 public resolvers what they return and marks which ones already have the change. When all of them return the new value, propagation is complete for those networks, and any others will follow within the TTL that was in place before the change. You can also query a specific resolver from the terminal with dig @8.8.8.8 yourdomain.com A.
Why do nameserver changes take up to 48 hours?
Because the delegation that points your domain to its nameservers is published by the registry of the extension, not by your DNS provider. For .com and .net it has a 48-hour TTL, so resolvers that cached the old nameservers can keep using them for up to two days, and lowering TTLs at the new provider doesn’t shorten that wait.
Does DNS propagation happen automatically?
Yes. Once you save a DNS change, there’s nothing to trigger: resolvers around the world pick it up on their own as their cached copies expire. The only ways to influence the speed are lowering the TTL before the change and flushing your local DNS cache to update your own device right away.
Conclusion
DNS propagation is a natural part of any domain change or server migration. While you cannot force it to happen instantly, understanding how it works — and preparing your TTL settings in advance — lets you decide how long the wait will be and reduces downtime.
To recap the key points from this guide: propagation takes as long as the TTL in place before the change; nameserver changes can take up to 48 hours; and lowering your TTL to 300 seconds at least 48 hours before a migration is the single most effective step you can take to speed things up.
To follow a change as it spreads, use the DNS propagation checker at the top of this page: enter the new value and it shows which resolvers already have it and how long the others will take.
For a deeper understanding of how DNS works as a whole — including record types, DNS security and how to change your DNS servers — see our complete guide: What does DNS stand for?
