How to Check DNS Propagation Step by Step
Have you recently changed your domain’s nameservers or DNS records and wondered why the changes are not visible everywhere yet? This is where DNS propagation becomes important.
When you update an A record, change nameservers, move a website to a new hosting provider, or switch DNS services, different DNS resolvers may continue using previously cached information for some time.
Knowing how to check DNS propagation can help you determine whether your DNS changes are reaching different locations or whether there is a configuration problem that needs attention.
In this guide, you’ll learn what DNS propagation means, how to check it, how TTL affects DNS updates, and what to do when your changes are not appearing as expected.
What Is DNS Propagation?
DNS propagation describes how updated DNS information becomes available through DNS resolvers and networks after a change.
For example, imagine that your website is currently hosted on Server A. You move it to Server B and change the domain’s A record to point to the new IP address.
Your authoritative DNS provider may already have the new record, but another DNS resolver may still have an older response stored in its cache.
That is why a DNS change can appear complete on your computer while someone in another location still sees the previous result.
DNS caching is an important part of this process because resolvers temporarily store DNS responses instead of requesting the same information from authoritative servers every time.
If you’re new to DNS, you can first read our guide on what DNS is and how it works to understand the basic concepts.
Why Does DNS Propagation Happen?
DNS caching helps reduce unnecessary DNS queries and can improve lookup efficiency.
A DNS record includes a TTL, or Time to Live, which tells resolvers how long a response can remain cached before it should be refreshed. Cloudflare’s DNS documentation explains that TTL controls how long DNS records are cached and therefore influences how quickly record updates reach users.
For example, a DNS record with a TTL of 3600 seconds represents one hour.
However, TTL isn’t a universal countdown that guarantees every device will update at exactly the same moment. Local caches, recursive resolvers, and other DNS behavior can affect when a user actually sees the new result.
This is why checking DNS from multiple resolvers is more useful than testing only from your own computer.
How to Check DNS Propagation
The easiest way to check DNS propagation is to use a reputable DNS checking service that queries your domain from multiple locations.
Before checking, identify exactly what you changed.
For example:
- A record
- AAAA record
- CNAME record
- MX record
- TXT record
- NS or nameserver records
You should check the same record type that you changed.
1. Identify the DNS Record You Changed
Start by determining exactly what was modified.
If you changed your website’s IP address, you will normally want to check the A record.
If your website uses IPv6, you may need to check the AAAA record.
If you changed where a subdomain points, check the relevant CNAME record.
If you changed your domain’s nameservers, check the NS records.
This first step prevents you from looking at the wrong DNS information.
2. Enter Your Domain Into a DNS Checker
Open a reputable DNS checking service and enter your domain name.
Choose the DNS record type you want to inspect.
For a website migration, an A-record lookup is usually the most relevant starting point.
For a nameserver change, inspect the NS records.
The goal is to compare the values returned from different locations rather than relying on a single DNS response.
3. Compare Results From Different Locations
A propagation checker can display DNS results from multiple geographic locations or DNS servers.
Look at the returned values carefully.
If most locations show your new IP address, the updated record is being returned by many resolvers.
If some locations still show an older IP address, those resolvers may still have cached information.
However, inconsistent results don’t automatically prove that normal propagation is the cause. Incorrect DNS configuration can also produce inconsistent behavior.
Cloudflare notes that DNS results can appear uneven because different resolvers may have queried the domain at different times or may apply different caching behavior.
4. Check Your Nameservers
If you recently moved your domain to a new DNS provider, check the NS records.
Your domain should be delegated to the nameservers provided by the DNS service that is supposed to manage your DNS zone.
If the nameservers are incorrect, checking individual A or CNAME records may not solve the problem because the domain may be asking the wrong DNS servers for its records.
This is especially important after:
- Changing hosting providers
- Moving DNS providers
- Transferring a domain
- Changing nameservers
- Rebuilding a DNS zone
What Is TTL and Why Does It Matter?
TTL stands for Time to Live.
It controls how long a DNS response can be cached by a resolver before it needs to be refreshed.
Common TTL values include:
- 300 seconds — 5 minutes
- 1800 seconds — 30 minutes
- 3600 seconds — 1 hour
- 86400 seconds — 24 hours
A longer TTL can reduce repeated DNS queries, but it can also mean that DNS changes take longer to appear through cached responses.
For example, if an old DNS response has a remaining TTL of 45 minutes, a resolver may continue returning that cached result until it expires.
That’s why changing a DNS record does not necessarily mean every user will immediately see the new value.
How Long Does DNS Propagation Take?
There is no single fixed propagation time that applies to every DNS change.
Some updates can become visible very quickly, while others may take longer depending on TTL values, resolver caching, the type of change, and DNS infrastructure.
If you recently changed DNS records, don’t immediately assume something is broken just because your own computer still shows the old result.
Instead:
- Check the authoritative DNS configuration.
- Check the relevant record type.
- Compare results from different resolvers.
- Check the TTL.
- Test again after some time.
If the configuration is correct but cached results remain, waiting for the relevant cache entries to expire may be necessary.
How to Check DNS Propagation Using Command Prompt
You can also check DNS information directly from Windows without relying entirely on an online tool.
Open Command Prompt and run:
nslookup example.com
Replace example.com with your own domain.
The result will show the DNS server being used and the address returned for the domain.
You can also query a specific DNS resolver.
For example:
nslookup example.com 8.8.8.8
This asks Google Public DNS to resolve the domain.
Google explains that Public DNS is a recursive DNS resolution service and uses authoritative DNS information to answer domain queries.
You can compare that result with another resolver:
nslookup example.com 1.1.1.1
If different resolvers return different results, investigate whether the difference is caused by caching, DNS configuration, or a recent change.
For more information about Google Public DNS, see the official Google Public DNS documentation.
How to Check DNS Propagation With Different Networks
Another useful test is to check your website using different internet connections.
For example, test it through:
- Home Wi-Fi
- Mobile data
- Another Wi-Fi network
- A different computer
- A different browser
You can also ask someone in another location to test the domain.
If your website displays the new server on one network but the old server on another, DNS caching may be involved.
However, this isn’t conclusive by itself. A DNS configuration problem can also produce different results.
Testing multiple networks simply gives you more evidence about where the problem may be occurring.
How to Check DNS Records More Closely
If a basic DNS checker shows unexpected results, inspect the actual DNS records.
Common DNS record types include:
A Record
An A record points a hostname to an IPv4 address.
For example:
example.com → 192.0.2.10
AAAA Record
An AAAA record points a hostname to an IPv6 address.
CNAME Record
A CNAME record points one hostname to another hostname.
For example:
www.example.com → example.com
MX Record
MX records specify the mail servers responsible for receiving email for a domain.
TXT Record
TXT records can store text-based DNS information and are commonly used for verification and email-related configurations.
Cloudflare’s DNS documentation provides additional details about common DNS record types and how they are represented.
What If DNS Propagation Is Not Complete?
If the DNS configuration is correct and some resolvers still show older information, the safest approach is usually to monitor the change rather than repeatedly editing the record.
Try these steps:
- Confirm the new DNS record.
- Verify your nameservers.
- Check the TTL.
- Compare multiple DNS resolvers.
- Test from another network.
- Wait and check again.
Avoid repeatedly changing the same DNS record while troubleshooting.
Every additional change makes it harder to determine which configuration is actually being tested.
What If DNS Changes Are Still Not Working?
Not every DNS issue is caused by propagation.
If your changes remain incorrect across multiple independent resolvers, check the configuration itself.
Check Your Nameservers
Verify that your domain uses the correct nameservers.
If the nameservers point to the wrong provider, the DNS records you’re editing may not be the records actually being used.
Check Your A Record
If you’re moving a website to a new server, make sure the A record contains the correct IP address.
An old IP address can cause users to reach the previous server.
Check for Conflicting Records
Look for old or duplicate records that could create unexpected results.
For example, an outdated A record may still exist while another record points to the new server.
Check Your Domain Status
Make sure the domain has not expired, been suspended, or otherwise entered a status that prevents normal resolution.
Check Your DNS Provider
If your configuration appears correct but the domain still behaves unexpectedly, contact the DNS provider or domain registrar.
If the website itself is unavailable, you can also read our guide on why your website may be down for additional troubleshooting steps.
DNS Propagation vs DNS Error: What’s the Difference?
These two situations are often confused.
DNS propagation refers to the process of updated DNS information becoming available through different resolvers and caches.
A DNS error occurs when DNS resolution fails or returns an unexpected response.
For example, after changing nameservers, some resolvers may return the new information while others temporarily return the previous result.
That’s different from a domain that consistently fails to resolve because its DNS configuration is missing or incorrect.
If you’re seeing DNS_PROBE_FINISHED_NXDOMAIN, our detailed guide on how to fix DNS_PROBE_FINISHED_NXDOMAIN covers that specific browser error.
Google Public DNS also documents how it handles queries for domains that do not exist and returns NXDOMAIN according to DNS protocol behavior.
Can You Flush DNS to Fix Propagation?
You can flush the DNS cache on your own device, but this does not force every DNS resolver on the internet to update.
For example, on Windows you can run:
ipconfig /flushdns
This clears the local DNS resolver cache.
However, upstream recursive resolvers may still have cached information. Cloudflare specifically notes that flushing a local DNS cache only affects the local device, not the upstream resolver.
If you’re troubleshooting a DNS problem on Windows, you may also want to read our guide on how to flush DNS cache if that article is already published on your site.
Common DNS Propagation Mistakes to Avoid
Changing DNS Records Repeatedly
Make one correct change and monitor the result.
Repeated edits make troubleshooting more difficult.
Checking Only One DNS Resolver
Your local DNS resolver isn’t necessarily representative of every location.
Compare multiple resolvers whenever possible.
Ignoring TTL
Cached DNS information may remain available until its relevant TTL expires.
Don’t assume that every resolver must update instantly.
Forgetting to Check Nameservers
A nameserver change affects which DNS servers are authoritative for your domain.
Always verify delegation before troubleshooting individual records.
Assuming Every DNS Problem Is Propagation
A wrong record, incorrect nameserver, expired domain, or DNS provider issue can look similar.
Always verify the actual DNS configuration.
When Should You Contact Your Domain or DNS Provider?
Contact your provider when:
- Your nameservers appear incorrect
- DNS records are missing
- Multiple independent resolvers return unexpected results
- Your domain has expired
- You cannot edit your DNS zone
- DNS changes remain incorrect after an appropriate caching period
- You suspect a DNS provider configuration problem
When contacting support, provide:
- Your domain name
- The DNS record you changed
- The old value
- The new value
- The date and time of the change
- Results from a few DNS checks
This information can help support staff understand the problem more quickly.
Frequently Asked Questions
How do I check DNS propagation?
Use a reputable DNS checking service to compare your domain’s DNS records from multiple locations and resolvers. You can also use nslookup on Windows to query individual DNS resolvers.
How long does DNS propagation take?
It varies. TTL values, resolver caching, the type of DNS change, and DNS infrastructure can all affect how quickly updated information becomes visible.
Can I check DNS propagation from Windows?
Yes. Windows includes the nslookup command, which can be used to inspect DNS responses from your default resolver or a specific DNS server.
Does flushing DNS speed up propagation?
No. Flushing your local DNS cache can remove cached information from your own computer, but it does not force external recursive resolvers to refresh their caches.
Why does my website work for me but not someone else?
Different users may be using different DNS resolvers or cached DNS information. It can also indicate an incorrect DNS configuration, so checking multiple resolvers is useful.
Does changing nameservers require DNS propagation?
Nameserver changes can take time to become visible through different DNS resolvers. After changing them, verify the NS records and monitor the results from multiple locations.
Can a high TTL delay DNS changes?
Yes. A longer TTL allows DNS responses to remain cached for longer, which can delay how quickly a new record is seen by some resolvers.
Final Thoughts
Learning how to check DNS propagation can make domain changes and website migrations much easier to troubleshoot.
Instead of relying on a single DNS lookup, check the exact record you changed, verify your nameservers, compare different DNS resolvers, and consider the record’s TTL.
If different locations gradually begin returning the same new DNS information, the change may simply be moving through cached responses.
If multiple independent resolvers continue returning incorrect results, investigate the DNS configuration instead of assuming you only need to wait.
A careful, step-by-step approach will help you distinguish normal DNS caching from an actual configuration problem.
