DNS Propagation Checker

Use the DNS Propagation Checker to check whether recent DNS changes are visible across public resolvers. If you changed hosting, updated A records, modified MX records, added TXT verification, changed name servers, or moved to a new DNS provider, this tool helps you see whether the new values are live.

DNS changes do not always appear everywhere at the same time. Resolver cache, TTL values, DNS provider updates, and network differences can cause some users to see old records while others already see the new ones.

What Is DNS Propagation?

DNS propagation describes the period during which DNS changes become visible across DNS resolvers and networks. When you update a DNS record, some resolvers may refresh quickly, while others may continue using cached data until the TTL expires.

This is why a domain may point to a new server for some users but still resolve to the old server for others. DNS propagation checking helps you understand whether the updated values are visible from different resolver perspectives.

Why DNS Propagation Matters

DNS propagation is important because DNS controls how users reach your website, email, APIs, subdomains, verification records, and many third-party services.

Propagation checks are useful after changes such as:

• Updating A or AAAA records after a hosting migration.
• Changing MX records for email migration.
• Adding TXT records for SPF, DKIM, DMARC, or domain verification.
• Changing CNAME records for SaaS or CDN setup.
• Updating NS records after moving DNS providers.
• Changing CAA records for SSL certificate issuance policy.

How to Use the DNS Propagation Checker

Using the IPMYP DNS Propagation Checker is simple.

1. Enter a domain or hostname, such as example.com or www.example.com.
2. Select the DNS record type you want to check when available.
3. Run the propagation check.
4. IPMYP checks DNS responses from public resolver perspectives.
5. Review whether the returned records match the expected new values.

For a broader technical review that includes DNS records, WHOIS, SSL, Ping, Traceroute, MTR, and other checks, use the main online network tools hub.

What Does a DNS Propagation Report Show?

A propagation report may show the DNS values returned by different resolvers or lookup paths.

• Domain or Host: The hostname being checked.
• Record Type: The DNS record type being tested, such as A, AAAA, MX, TXT, CNAME, NS, or CAA.
• Returned Value: The DNS answer returned by each resolver.
• Status: Whether the resolver returns the expected value, old value, or no result.
• TTL: The cache lifetime for the DNS answer when available.

When Should You Check DNS Propagation?

You should check DNS propagation whenever a DNS change needs to become visible publicly.

After Moving a Website

When you move a website to a new host or server, you usually update A or AAAA records. A propagation check helps confirm whether the new server IP is visible.

After Changing Email Provider

When moving email to Google Workspace, Microsoft 365, Zoho, or another provider, MX and TXT records must update correctly. DNS propagation checks help confirm whether those records are live.

After Adding Domain Verification Records

Many SaaS, CDN, analytics, and email platforms ask you to add TXT or CNAME verification records. If verification fails, propagation may not be complete yet.

After Changing Name Servers

Name server changes can take longer to settle than simple record changes. During that transition, some resolvers may still query the old DNS provider.

DNS Propagation and TTL

TTL, or Time To Live, controls how long DNS resolvers may cache a record. A lower TTL can make planned DNS changes appear faster, while a higher TTL can cause old values to remain cached longer.

Before planned migrations, many administrators lower TTL in advance, wait for old cache values to expire, make the change, then raise TTL again after everything is stable.

DNS Propagation vs DNS Delegation

DNS propagation and DNS delegation are related but different.

• DNS Propagation: Checks whether DNS record changes are visible across resolvers.
• DNS Delegation: Checks whether the domain points to the correct authoritative name servers.

If records are not updating because the domain is still delegated to the wrong DNS provider, use DNS Delegation Check to verify the active name servers.

DNS Propagation and Email Security

Email DNS changes often depend on propagation. SPF, DKIM, DMARC, and MX records may take time to become visible after being added or updated.

If email authentication still fails after DNS changes, use Email Security Check to review published SPF, DKIM, DMARC, and MX records once propagation has completed.

DNS Propagation and CAA Records

CAA changes may affect SSL certificate issuance. If you recently changed which Certificate Authority is allowed to issue certificates, DNS caching may cause old CAA values to remain visible for a while.

Use CAA Record Lookup to check the currently visible certificate authority policy for your domain.

Common DNS Propagation Problems

• The DNS record was added to the wrong DNS provider.
• The domain is still delegated to old name servers.
• TTL is high and old values are still cached.
• The record was created for the wrong hostname.
• The value was copied incorrectly.
• Some resolvers return old values while others return new values.
• DNSSEC or delegation problems prevent valid resolution.

Best Practices for DNS Changes

• Lower TTL before planned migrations when possible.
• Confirm which DNS provider is authoritative before editing records.
• Document old and new DNS values before making changes.
• Check propagation after changing A, MX, TXT, CNAME, NS, or CAA records.
• Verify website, email, SSL, and subdomains after changes.
• Use DNS delegation checks when records do not appear from the expected provider.
• Allow enough time for resolver cache to expire before assuming a change failed.

Frequently Asked Questions

What does a DNS Propagation Checker do?

A DNS Propagation Checker checks whether DNS changes are visible across resolvers and whether the current DNS answer matches the expected value.

How long does DNS propagation take?

DNS updates may appear within minutes, but full visibility can take longer depending on TTL values, resolver cache, registry updates, and DNS provider behavior.

Why do I still see the old IP address?

You may still see the old IP because your resolver has cached the previous DNS answer, the TTL has not expired, or the record was updated at the wrong DNS provider.

Does clearing browser cache fix DNS propagation?

Browser cache can affect some behavior, but DNS propagation depends mainly on DNS resolver cache and authoritative DNS settings. Clearing local DNS cache may help for your device, but it does not update global resolvers.

Why does one resolver show the new record and another show the old one?

Different resolvers may cache records independently. Some may refresh quickly, while others continue serving old values until their cache expires.

What should I check if propagation never completes?

Check whether the domain is delegated to the correct name servers, whether the record was added to the active DNS provider, whether DNSSEC is valid, and whether the hostname and value are correct.

Check DNS Propagation Online With IPMYP

IPMYP’s DNS Propagation Checker helps you verify whether DNS changes are visible across resolvers. Enter a domain above, select the record type, run the check, and review whether the latest DNS values are active for your domain, website, email, SSL, or verification setup.