IT
OmnvertObrazy • Dokumenty • Sieć

DNS Propagation Checker

Query A/AAAA/CNAME/TXT/MX/NS records. Recursive vs Authoritative views help catch stale caches or misconfigurations.

Recursive results

Waiting…

Authoritative results

Waiting…

How it works

The tool asks your server to resolve the domain and returns answers as seen by a recursive resolver. Authoritative view queries the domain’s NS to bypass caches (enable /api/network/dns-check-authority).

Tips: after DNS changes, start with NS answers to confirm the zone, then compare with recursive results. Check TTLs and consider CDN propagation delays.

O narzędziu

Use this DNS checker to confirm which records are visible on the internet. It’s helpful after DNS changes (new A record, MX setup, SPF/DKIM updates) when you want to verify that resolvers return the expected values.

DNS propagation is not always instant. Some resolvers cache results based on TTL, and authoritative misconfigurations can cause inconsistent responses. This tool makes it easier to compare what different lookups return so you can identify where the mismatch happens.

For email deliverability, DNS is especially critical: MX, SPF, DKIM and DMARC must be correct. If your site is not reachable, A/AAAA and CNAME records are often the first place to check.

FAQ

How long does DNS propagation take?
It depends on TTL and resolver caching. Some changes appear quickly, others may take hours.
What is TTL?
TTL is how long resolvers can cache a DNS answer before asking again from authoritative servers.
Why do different resolvers show different results?
Caching, geo routing, split-horizon DNS, or inconsistent authoritative records can cause differences.
Which records matter for websites?
A/AAAA and CNAME are common for web traffic. NS indicates authoritative name servers.
Which records matter for email?
MX for mail routing, TXT for SPF/DKIM/DMARC policies and verification.

Powiązane narzędzia