What is DNS Propagation?
When you add, update, or delete a DNS record, the change does not take effect instantly worldwide. Instead, the update must spread ("propagate") from your domain's authoritative nameservers to DNS resolvers and caches operated by ISPs, CDNs, and public DNS services like Google and Cloudflare around the globe. This spreading process is called DNS propagation.
The time it takes depends primarily on the TTL (Time to Live) value set on your DNS record — a 300-second TTL means caches hold the old record for up to 5 minutes; a 86400-second TTL means 24 hours. Most providers default to TTL values between 300 and 3600 seconds. Because different resolvers cached the old record at different times, propagation can appear partial for some time — some users will see the new record while others still see the old one.
How to Use This DNS Propagation Checker
1
Enter your domain
Type the domain name (e.g. example.com or subdomain.example.com). Omit the protocol — no https:// needed.
2
Select the record type
Choose the DNS record type you changed: A for website IP, MX for mail servers, TXT for SPF/DKIM, NS for nameserver changes (during registrar migrations).
3
Click Check Propagation
The tool queries 6 major DNS resolvers sequentially, showing the result from each in real time as each query completes.
4
Interpret the summary
100% means all checked resolvers return the new record. Less than 100% means propagation is still in progress — wait and re-check. Compare the answers across resolvers to spot any discrepancies.
📊 How Long Does DNS Propagation Take?
💡 Real-World Use Cases
🌐
Website Migration
When moving a site to a new hosting provider, lower the A/AAAA record TTL 24h before migration. After pointing to the new server, use this tool to confirm the new IP is propagated before decommissioning the old server.
📧
Email Configuration
After adding MX, SPF, or DKIM TXT records, use this checker to confirm the records have propagated before enabling production email — sending before propagation complete can cause delivery failures.
🛡️
SSL Certificate Issuance
Let's Encrypt and other CAs verify domain control via DNS TXT records (ACME DNS-01 challenge). If propagation is incomplete when the CA checks, certificate issuance fails. Verify propagation first.
🔢
Registrar Transfer
NS record changes during a registrar transfer are the slowest to propagate (24–72 hours). Monitor NS propagation with this tool and keep the old nameservers live until the new ones are fully confirmed everywhere.
📜 DNS Propagation vs DNS Caching
⚡ Propagation Best Practices
To minimise downtime and user impact during DNS changes: (1) Lower TTL to 300 seconds at least 24 hours before making changes. (2) Make the DNS record change. (3) Use this propagation checker to monitor spread. (4) Keep old resources (old IP, old mail server) live for at least one full propagation cycle. (5) After confirming full propagation, decommission old resources and optionally raise TTL back to a higher value for performance. For complex migrations involving nameserver changes, consider using multiple DNS propagation tools from different global perspectives, and always test with our DNS Lookup tool after propagation is confirmed.
Why does DNS propagation take so long? +
DNS propagation takes as long as the TTL value on the previous record — resolvers cache records and won't refresh until the TTL expires. A 24-hour TTL means each resolver holds the old record for up to 24 hours. Lowering TTL in advance of planned changes dramatically speeds up propagation.
What is a DNS TTL? +
TTL (Time to Live) is a value in seconds attached to every DNS record, instructing resolvers how long to cache it before asking the authoritative nameserver for a fresh copy. A TTL of 3600 means the record is cached for 1 hour. Lower TTLs = faster propagation but higher load on nameservers.
Why do some resolvers show the new record and others the old one? +
Each resolver cached the old record at a different point in time. A resolver that cached it just before your change will hold the old value until its TTL expires, while one that hadn't cached it yet will fetch the new value immediately. This partial propagation is completely normal.
How can I speed up DNS propagation? +
The most effective method: reduce the TTL of the record you plan to change to 60–300 seconds at least 24 hours before making the change. Once the old low TTL is propagated everywhere, make your DNS change — resolvers will now refresh within 1–5 minutes. After migration is confirmed, restore TTL to normal.
What is NXDOMAIN in DNS? +
NXDOMAIN (Non-Existent Domain) means the DNS resolver could not find any records for the queried domain at all — not just the record type you requested, but the domain itself. This can mean the domain doesn't exist, has expired, or its nameservers aren't responding correctly.
How do I check DNS propagation for a specific country? +
This tool queries globally distributed resolvers (Google, Cloudflare, Quad9) which serve users worldwide. For highly specific regional testing, you can also use local ISP DNS servers (check your router settings) or tools that offer country-specific resolver selection.
How long do nameserver (NS) changes take to propagate? +
NS record changes (nameserver delegation) are the slowest DNS changes, typically taking 24–72 hours. This is because the parent zone (registry) must also update its delegation records, and registrars must submit those changes upstream. Always keep old nameservers active for the full 72-hour window.
Does DNS propagation affect email delivery? +
Yes. Changes to MX, SPF (TXT), or DKIM records must fully propagate before they take effect on sending/receiving. During propagation, some mail servers will use the old records. Always verify MX and TXT propagation using this tool before routing production mail through changed records.
Can I flush or force DNS propagation? +
You can flush your own device/browser DNS cache (Windows: ipconfig /flushdns; Mac: dscacheutil -flushcache) and Google's public cache at google.com/webhp — search for your domain. However, you cannot force third-party resolvers to expire their cache early; only TTL expiry triggers a refresh.
What does 100% propagation mean? +
It means all checked resolvers are returning the new record. In practice, there may be obscure or regional resolvers that haven't updated yet. 100% on this checker (covering Google, Cloudflare, Quad9 and others) is a strong indicator that propagation is complete for most users globally.
Why do I see my new DNS record immediately but others don't? +
Your device or local ISP resolver may have expired its cache (or never cached the old record) and fetched the new value. Other users' ISP resolvers are still serving the cached old record. This is expected — they'll see the new record once their cache TTL expires.
What is DNS over HTTPS (DoH)? +
DNS over HTTPS encrypts DNS queries using HTTPS instead of sending them as plain-text UDP. This tool uses DoH endpoints (dns.google, cloudflare-dns.com, dns.quad9.net) to query resolvers, which also ensures queries work even when firewalls block traditional port 53 DNS traffic.
Can I check propagation for a subdomain? +
Yes. Enter the full subdomain (e.g. mail.example.com, www.example.com, api.example.com) and select the appropriate record type. Subdomains are treated as independent DNS entries and may propagate at different speeds depending on their individual TTL values.
Is this DNS propagation tool free? +
Yes — completely free, no sign-up required, and no query limits. Results are live, querying real DNS resolvers in real time. No data is stored on our servers.
How is this different from the DNS Lookup tool? +
Our
DNS Lookup tool queries a single resolver for all record types at once — ideal for general DNS investigation. This propagation checker specifically queries multiple resolvers for one record type to verify that a recent change has spread globally, making it the right tool post-change.