DNS Leak Checker

DNS Propagation Check – See If Your DNS Has Updated Worldwide

When you make changes to your DNS records — updating an A record, adding an MX record, or changing nameservers — those changes do not take effect instantly across the entire internet. DNS propagation is the process by which your updated records spread to DNS servers worldwide, and it can take anywhere from a few minutes to 48 hours depending on your TTL settings and DNS provider. This free tool checks whether your DNS changes are visible right now, helping you confirm propagation status without waiting and guessing. Enter your domain below to check any DNS record type instantly.

What Is DNS Propagation?

DNS propagation is the time it takes for changes made to your DNS records to be recognised and reflected by DNS servers across the internet. When you update a DNS record at your domain registrar or hosting provider, that change is made immediately in your authoritative DNS server — the server that holds the official record for your domain. However, DNS resolvers worldwide cache DNS records for a period of time determined by the TTL (Time to Live) value set on each record.

TTL is measured in seconds and tells DNS resolvers how long to cache a record before requesting a fresh copy from the authoritative server. A TTL of 3600 means DNS resolvers will cache your record for one hour before checking for updates. A TTL of 86400 means they will cache it for 24 hours. If you change a DNS record that had a high TTL set, resolvers that already cached the old record will continue serving the old value until their cache expires — regardless of when you made the change.

This creates a window where different users around the world see different DNS records for your domain — some see the old record from their cached copy, while others who query a fresh copy from the authoritative server see the updated record. This period of inconsistency is what people mean when they say they are "waiting for DNS to propagate." It is a normal part of how the DNS system works and not a sign of an error.

The most commonly changed DNS records are A records (which point your domain to an IP address, changed when migrating web hosting), MX records (which route email, changed when migrating email providers), CNAME records (aliases that point one subdomain to another domain, common for CDN configuration), and NS records (nameservers, changed when switching DNS providers — this has the longest propagation time of all record types, sometimes taking the full 48 hours).

Professional developers and system administrators commonly reduce TTL values to 300 seconds (5 minutes) 24–48 hours before making DNS changes. This means that when the change is made, resolvers refresh their cached records within 5 minutes rather than waiting for the original long TTL to expire. After the migration is confirmed stable, TTL can be increased back to a higher value. Planning TTL reduction before changes is the single most effective way to reduce DNS propagation time.

DNS propagation time also varies by geography. Major internet hubs like the US, UK, Germany, and Singapore tend to propagate DNS changes faster than more remote regions due to denser DNS infrastructure and higher query volumes that force more frequent cache refreshes. If your website is primarily for a specific region, confirming propagation in that region is more important than a global check — though this tool checks the DNS response from your current location which is often sufficient for most users.

How to Read Your DNS Propagation Results

A successful DNS propagation check shows the current record value returned by the DNS system. For an A record, this is the IP address your domain currently resolves to. If this matches the IP address of your new hosting server, propagation has completed in the DNS path being tested. If it still shows the old IP address, propagation has not yet completed on the resolvers being queried.

The TTL value shown in the results is the remaining cache time in seconds. A low TTL (under 300) means the record will refresh shortly and propagation should complete soon. A high TTL (3600 or above) means the cached record has a long time remaining before it refreshes. If you see a high TTL on an old record value, you may need to wait several hours before checking again.

A "No DNS record found" result for a domain that should exist can mean several things: the domain has recently expired, the record type you are checking does not exist for that domain, the nameserver change is still propagating (in which case the authoritative server is temporarily unreachable from some paths), or the domain is not yet fully active. Try checking again with a different record type — if an NS record resolves but an A record does not, your nameservers are live but the A record has not yet propagated.

Common DNS Record Types Explained

A Record

An A record maps a domain name to an IPv4 address, telling DNS resolvers which server to direct visitors to when they type your domain into a browser. It is the most fundamental DNS record type and the one most frequently changed during website migrations. You would change your A record when moving your website to a new hosting provider, setting up a new server, or pointing your domain to a different IP address.

AAAA Record

An AAAA record is the IPv6 equivalent of an A record, mapping a domain name to a 128-bit IPv6 address instead of a 32-bit IPv4 address. As the internet transitions from IPv4 to IPv6, AAAA records are increasingly important for ensuring your domain is accessible to users on IPv6-only networks. You would add or change an AAAA record when your hosting provider assigns you an IPv6 address or when you want to ensure full dual-stack (IPv4 + IPv6) accessibility for your domain.

MX Record

An MX (Mail Exchange) record specifies the mail server responsible for receiving email on behalf of your domain. MX records include a priority value that determines which server is tried first if you have multiple mail servers configured. You would change your MX record when switching email providers — for example, migrating from a self-hosted mail server to Google Workspace or Microsoft 365.

CNAME Record

A CNAME (Canonical Name) record creates an alias that points one domain or subdomain to another domain name rather than directly to an IP address. It is commonly used to point subdomains like www.example.com to example.com, or to point a subdomain to a CDN or SaaS provider's domain. You would add or change a CNAME record when setting up a CDN like Cloudflare, configuring a SaaS tool on a custom subdomain, or creating domain aliases.

TXT Record

A TXT record stores arbitrary text data associated with your domain and is used for domain verification, email authentication, and security policies. Common uses include SPF records (which specify which servers are authorised to send email for your domain), DKIM keys (email signing), and DMARC policies (email authentication reporting). You would add TXT records when setting up email authentication, verifying domain ownership for services like Google Search Console, or implementing security policies.

NS Record

An NS (Name Server) record specifies which DNS servers are authoritative for your domain — meaning which servers hold the official DNS records for your domain. NS records are set at the domain registry level and determine where all other DNS queries for your domain are directed. You would change your NS records when switching DNS hosting providers, such as moving from your registrar's default DNS to Cloudflare, AWS Route 53, or another managed DNS service.

How to Speed Up DNS Propagation

  1. Step 1 — Lower Your TTL Before Making Changes: At least 24–48 hours before making any DNS change, reduce the TTL on the record you plan to change to 300 seconds (5 minutes). This ensures that by the time you make the actual change, most resolvers worldwide have already switched to the short cache duration. When you then update the record, resolvers refresh within minutes rather than hours.
  2. Step 2 — Use a Fast Authoritative DNS Provider: Your authoritative DNS provider's infrastructure directly affects how quickly resolvers can fetch updated records. Providers like Cloudflare, AWS Route 53, and Google Cloud DNS operate global Anycast networks that respond to queries from the nearest data centre, reducing lookup time and accelerating propagation. Slower providers with fewer points of presence can create bottlenecks that delay propagation.
  3. Step 3 — Flush Your Local DNS Cache After Changes: After making DNS changes, flush your device's local DNS cache to see the new records immediately on your own machine. On Windows, open Command Prompt and run ipconfig /flushdns. On Mac, open Terminal and run sudo dscacheutil -flushcache. This does not affect propagation globally but ensures you are not looking at stale cached data locally.
  4. Step 4 — Flush Your Browser DNS Cache: Modern browsers maintain their own DNS cache separate from the operating system. In Chrome, navigate to chrome://net-internals/#dns and click "Clear host cache". In Firefox, the browser cache is cleared when you restart it. Without clearing the browser cache, you may continue to see old DNS records even after flushing the OS-level cache.
  5. Step 5 — Test From Multiple Locations: Use DNS propagation checking tools (like this one) to verify your changes are visible. Testing from a single location only confirms propagation on that specific resolver path. For critical migrations, confirm that the correct records are returned by multiple DNS providers including Google (8.8.8.8) and Cloudflare (1.1.1.1) to get a broader picture of global propagation status.
  6. Step 6 — Wait for the Old TTL to Expire Before Expecting Results: Even with optimal preparation, some resolvers may have cached the old record with the previous high TTL value. The absolute maximum propagation time is determined by the TTL that was set on the old record before you changed it. If the old TTL was 86400 (24 hours), expect up to 24 hours for complete global propagation — there is no way to override another resolver's cache from the outside.

DNS Propagation vs DNS Leak — What's the Difference?

DNS propagation and DNS leaks are two completely different concepts that happen to both involve the Domain Name System. DNS propagation refers to the time it takes for changes to DNS records — such as updating an A record or changing nameservers — to spread across DNS servers worldwide. It is relevant to website owners, developers, and system administrators who are making changes to their domain's DNS configuration and need to confirm those changes have taken effect globally.

A DNS leak, by contrast, is a privacy vulnerability where your DNS queries bypass your VPN tunnel and are sent directly to your ISP's DNS servers, exposing every website you visit to your ISP despite your VPN appearing to be connected. DNS leaks are relevant to privacy-conscious users who rely on a VPN to hide their browsing activity. If you are concerned about DNS privacy rather than DNS propagation, run a DNS leak test to check whether your VPN is properly protecting your DNS queries.

We may earn a commission if you purchase through our link

You cannot force DNS propagation globally — each resolver on the internet maintains its own cache and refreshes independently based on TTL values. However, you can force propagation on your own device by flushing your local DNS cache. On Windows, run ipconfig /flushdns in Command Prompt. On Mac, run sudo dscacheutil -flushcache in Terminal. You can also switch your device to use a public DNS resolver like Cloudflare (1.1.1.1) or Google (8.8.8.8), which tend to refresh cached records faster than ISP DNS servers. For future changes, the best approach is proactive: lower your TTL well before making changes so propagation is nearly instant when the change occurs.

Frequently asked questions

How long does DNS propagation take?

DNS propagation typically takes anywhere from a few minutes to 48 hours, depending on several factors including the TTL (Time to Live) value previously set on the record being changed, the DNS provider you are using, and the geographic location of the DNS resolvers involved. Records with low TTL values (300 seconds or less) propagate within minutes because resolvers refresh their cache frequently. Records with high TTL values (86400 seconds / 24 hours) can take a full day before all resolvers worldwide have the updated record. Nameserver (NS) changes tend to take the longest because they involve coordination between the domain registry and the authoritative DNS servers.

How do I know when DNS propagation is complete?

DNS propagation is complete when DNS resolvers across the internet return the new record value instead of the old one. You can verify this by running a DNS lookup using this tool and checking that the returned record matches your expected new value. If the record value shown matches what you configured at your DNS provider, propagation has completed for the resolver path you are testing. For critical migrations, test from multiple locations or use multiple DNS checking services to confirm global propagation rather than relying on a single check.

Why are some users seeing my old website after I migrated?

After changing your A record to point to a new hosting server, users whose DNS resolver still has the old record cached will continue to be directed to the old server. This is not an error — it is the normal behaviour of DNS caching working as designed. Users whose resolvers have refreshed their cache will see the new site, while those with cached copies of the old record continue to see the old site until their cache expires. The duration of this split depends entirely on the TTL that was set on the old A record before you made the change. To minimise this window, reduce your TTL to 300 seconds at least 24 hours before making the migration.

What is TTL and how does it affect propagation speed?

TTL stands for Time to Live and is a value set on every DNS record measured in seconds. It tells DNS resolvers how long they are allowed to cache the record before they must request a fresh copy from the authoritative DNS server. A TTL of 3600 means resolvers will use their cached copy for one hour before checking for updates. A TTL of 300 means they will refresh every 5 minutes. Lower TTL values result in faster propagation of changes but increase the number of queries to your authoritative DNS server, which can affect performance for very high-traffic domains.

How do I speed up DNS propagation?

The most effective way to speed up DNS propagation is to reduce your TTL value to 300 seconds (5 minutes) at least 24-48 hours before making your DNS change. This ensures that by the time you make the actual change, most resolvers worldwide have the low TTL cached and will refresh within minutes. After the change has propagated and the new configuration is confirmed stable, increase the TTL back to a higher value (3600-86400) for optimal caching performance. You can also flush your local DNS cache immediately after making changes to see the new records on your own device right away.

Why does my DNS show as propagated in one country but not another?

Different DNS resolvers around the world cache records independently and refresh at different times based on when they last queried the record. A resolver in the US may have cached your old record 5 minutes ago (and will refresh soon), while a resolver in Japan may have cached it 23 hours ago (and will also refresh soon, but from a different starting point). Large ISPs operate their own resolvers which cache independently from public DNS providers like Google and Cloudflare. Geographic differences in DNS infrastructure density also play a role — regions with more DNS resolvers tend to propagate faster due to higher query volumes forcing more frequent cache refreshes.

Does changing nameservers take longer than changing A records?

Yes, nameserver changes (NS records) typically take longer to propagate than A record changes. When you change nameservers, the update must propagate through the domain registry (like Verisign for .com domains), which adds an additional layer of propagation time. The registry updates its own records on a schedule that can take up to 48 hours, and only after the registry has updated can downstream resolvers begin to see the new nameservers. In contrast, A record changes are made directly on your authoritative DNS server and begin propagating immediately to resolvers whose cache has expired.

Can I force DNS propagation to complete faster?

You cannot force DNS propagation globally — each resolver on the internet maintains its own cache and refreshes independently based on TTL values. However, you can force propagation on your own device by flushing your local DNS cache. On Windows, run ipconfig /flushdns in Command Prompt. On Mac, run sudo dscacheutil -flushcache in Terminal. You can also switch your device to use a public DNS resolver like Cloudflare (1.1.1.1) or Google (8.8.8.8), which tend to refresh cached records faster than ISP DNS servers. For future changes, the best approach is proactive: lower your TTL well before making changes so propagation is nearly instant when the change occurs.

Stop leaks for good

A VPN with private DNS on every server, a kill switch and WebRTC protection closes every leak this site tests for.

Get NordVPN →

30-day money-back guarantee · We may earn a commission