SysAdmin Tools

A DNS propagation checker lets you verify how DNS record changes are spreading across DNS resolvers around the world. When you update a DNS record — change an A record to point to a new server, update MX records to a new mail provider, or modify nameservers after a domain transfer — the change does not appear instantly everywhere. Propagation takes time determined by the TTL (Time to Live) of the old record, and different resolvers around the world update at different speeds.

Understanding DNS propagation is critical for anyone managing websites, mail infrastructure, or any internet-connected service. During a propagation window, some users see old records while others see the new ones — causing inconsistent behaviour, failed logins, undelivered email, and confusing support requests. Knowing the propagation status lets you communicate accurately with users and diagnose whether problems stem from incomplete propagation or an actual misconfiguration.

Our DNS propagation tool checks your domain's DNS records from multiple resolver locations across North America, Europe, Asia, and Oceania simultaneously, showing you the current state from each vantage point. You can see instantly which regions are serving the new record and which are still caching the old value.

Propagation time varies widely: records with a TTL of 300 seconds (5 minutes) propagate within minutes, while records with a TTL of 86400 (24 hours) can take a full day to update everywhere. Always lower the TTL of a record well in advance of a planned DNS change to minimise the propagation window.

How to Use the DNS Propagation Checker

  1. 1

    Enter the domain name

    Type the domain whose DNS changes you want to track — for example, example.com or mail.example.com. Enter the full hostname if you are tracking a subdomain.

  2. 2

    Select the record type

    Choose the DNS record type you changed: A (server IP), AAAA (IPv6), MX (mail server), TXT (SPF, DKIM), NS (nameservers), or CNAME. Select the type that corresponds to the change you made.

  3. 3

    Click Check Propagation

    The tool simultaneously queries DNS resolvers in multiple global locations and returns the record value seen from each location. Results appear within seconds.

  4. 4

    Monitor until propagation is complete

    Compare results across locations. Locations still showing the old record value have not yet propagated. Refresh periodically until all locations show the new value, confirming propagation is complete.

Understanding DNS Propagation Results

The propagation checker shows a table of DNS resolver locations, each with the record value they are currently returning for your query. Consistent results (same value from all locations) means propagation is complete — all resolvers are serving the new record. Mixed results mean propagation is in progress — some resolvers have refreshed their cache while others are still serving the old TTL-cached value. The time shown for each location is the query time (latency from our checker to that resolver). The record value is what that resolver is currently serving — this may be the old value, the new value, or NXDOMAIN (no record found). If you see the new record from some locations but not others, propagation is working correctly and will complete once the old record's TTL expires on remaining resolvers. If you see the old record everywhere even after the expected TTL has elapsed, there may be a TTL misconfiguration or the DNS change was not saved correctly.
FieldDescription
LocationThe geographic region of the DNS resolver queried — e.g. US East, EU West, Asia Pacific.
StatusWhether the resolver returned a record (propagated), no record (not yet propagated), or an error.
Record ValueThe DNS record value currently returned by that resolver — the IP address, hostname, or text data.
TTLTime to Live remaining on the cached record at this resolver. When it reaches zero, the resolver re-queries the authoritative nameserver.
Query TimeLatency in milliseconds between the checker and that resolver. Higher latency may indicate a geographically distant resolver.

Common DNS Propagation Use Cases

Monitor a server migration after updating A records

After pointing your domain's A record to a new server IP, use the propagation checker to track which regions have switched to the new server. This tells you when it is safe to decommission the old server and helps identify regions where users may still be hitting the old IP.

Verify nameserver propagation after a domain transfer

After transferring a domain to a new registrar and updating nameservers, the propagation checker shows when the new nameservers are authoritative worldwide. Until propagation is complete, DNS queries from some regions go to the old nameservers, which may have outdated or missing records.

Track email MX record propagation

After migrating from one email provider to another and updating MX records, monitor propagation to know when all incoming email will route to the new mail servers. Email sent during the propagation window may still arrive at the old server, which is why keeping the old server running during this period is important.

Confirm SPF or TXT record changes have propagated

After adding a new email sending service to your SPF record or publishing a new DKIM key, verify the changes are visible from resolvers worldwide before completing the email service setup. Activating a new sending service before its DKIM or SPF record has propagated causes authentication failures.

DNS Propagation — Frequently Asked Questions

What is DNS propagation?
DNS propagation is the time it takes for a DNS record change to spread across all DNS resolvers worldwide. When you update a DNS record, the change is made on your authoritative nameserver immediately. But DNS resolvers around the internet cache records for a period defined by the record's TTL. Until each resolver's cache expires and it re-queries the authoritative nameserver, it continues serving the old record.
How long does DNS propagation take?
DNS propagation time equals the TTL (Time to Live) of the old record. If the old A record had a TTL of 3600 seconds (1 hour), propagation completes within one hour for most resolvers worldwide. Records with a TTL of 86400 (24 hours) can take a full day. Some resolvers extend propagation time by violating TTL and caching longer than specified. The commonly cited "24-48 hours for DNS to propagate" is a worst-case estimate for high-TTL records.
How can I make DNS propagation faster?
Lower the TTL of the record before making the change. Best practice: at least 24 hours before a planned DNS change, reduce the record's TTL to 300 seconds (5 minutes). Once the change is made and verified, restore the TTL to its normal value (3600 or higher). This limits the propagation window to 5 minutes instead of hours or days. You cannot speed up propagation retroactively once a change is made with a high TTL.
Why do I see different DNS results from different locations?
Different locations see different DNS results during propagation because each DNS resolver has its own cache. When a resolver's cached copy of a record expires, it fetches the new value from the authoritative nameserver. Resolvers in different regions query at different times, so during the propagation window some see the new record and others still serve the old one. This is expected behaviour, not an error.
What is a DNS resolver?
A DNS resolver (also called a recursive resolver) is a server that handles DNS queries on behalf of clients. When you type a domain into a browser, your operating system sends a query to a resolver (typically your ISP's resolver, Cloudflare 1.1.1.1, Google 8.8.8.8, etc.). The resolver looks up the answer — either from its cache or by querying authoritative nameservers — and returns the result. The DNS propagation checker queries resolvers in multiple geographic locations to show the global picture.
What is TTL and how does it affect propagation?
TTL (Time to Live) is a value in seconds attached to each DNS record that tells resolvers how long they may cache it before re-querying. A TTL of 300 means the record is cached for 5 minutes. A TTL of 86400 means 24 hours. After the TTL expires, the resolver fetches a fresh copy from the authoritative nameserver — picking up any changes. Shorter TTLs speed up propagation; longer TTLs reduce DNS query load at the cost of slower change propagation.
Why is my DNS change showing old results after the TTL has expired?
Some DNS resolvers cache longer than the specified TTL in violation of the RFC. Others have negative TTL caching for NXDOMAIN responses. Check that your authoritative nameserver actually has the new record (query it directly with dig @your-nameserver example.com). If the authoritative nameserver shows the new record but resolvers still show the old one, wait an additional few hours and check again.
What is the difference between DNS propagation and DNS TTL?
TTL is the mechanism; propagation is the process. The TTL value on a DNS record determines how long it stays cached. Propagation is the end-to-end process of a DNS change becoming visible on all resolvers worldwide — which is essentially the wait for every cached copy to expire. The propagation time is therefore determined by the TTL of the old record at the time the change is made.
Does DNS propagation affect email delivery?
Yes, MX record propagation directly affects email delivery. During propagation, some sending mail servers will still deliver email to your old mail server while others deliver to the new one. This is why you should keep the old mail server running until propagation is complete. For SPF and DKIM TXT record propagation, email sent from new sending services before propagation is complete will fail authentication checks on resolvers that have not yet seen the new records.
How do I check DNS propagation from the command line?
Use dig to query specific resolvers: dig @8.8.8.8 example.com A queries Google's resolver; dig @1.1.1.1 example.com A queries Cloudflare. Run the same command against multiple resolvers to compare results. For nameserver changes, query the authoritative nameservers directly: dig @ns1.registrar.com example.com NS. Our online propagation checker automates this process across dozens of global locations simultaneously.

Related Tools