DNS Propagation Checker - How to Validate DNS Updates Worldwide
DNS changes don’t show up everywhere instantly. With the DNS Propagation Checker on
tools.edeskcloud.com, you can validate DNS results from different resolvers and confirm whether your new record values are being served globally.
Instead of only showing plain text responses, a modern propagation tool can also visualize results on a world map to make regional issues easier to spot.
This is useful after you update your website IP, switch nameservers, change email routing, or add verification TXT records for services like
Google Workspace or Microsoft 365. The goal is simple: confirm that your intended records are live and consistent.
How to Add a Custom DNS Server
Some tools allow adding your own resolver for testing (for example, an ISP resolver or a private DNS node).
Typically, you add:
- DNS Name (required)
- DNS IP (required)
- DNS Provider
- Map Latitude
- Map Longitude
Once added, a propagation checker can include that DNS server in the public list (optional) so it shows up in future checks.
How to Set an “Expected Value” (IP / Text)
If you’ve just updated your website IP or a specific TXT entry, it’s helpful to define an expected value so you can quickly see
which resolvers are returning the new value and which are still cached.
A good propagation checker can support matching rules like:
exact match, contains, or regex pattern (useful for TXT records that include long verification strings).
What DNS Is and Why It Matters
The Domain Name System (DNS) is a hierarchical and distributed naming system that maps domain names to IP addresses.
It works like a directory: people type a domain, networks use an IP.
How DNS Resolution Works
When you open a website, DNS resolution translates the domain name into a server IP. Multiple DNS systems work together in sequence:
- Recursive resolver (DNS resolver): receives the query from your device and tries to answer from cache.
- Root servers: guide resolvers to the correct TLD (like .com, .net, .org).
- TLD nameservers: respond with the authoritative nameservers for the domain.
- Authoritative nameservers: return the final DNS record values for the domain zone.
What DNS Propagation Means
DNS propagation is the time it takes for DNS updates to spread across caches worldwide. In some situations it can take
up to 48 hours (worst-case), depending on TTL and resolver caching behavior.
If you changed records and still see old values, it’s usually cache-related. Resolvers refresh after TTL expiry, so different regions can show different results temporarily.
Common Reasons DNS Looks “Stuck”
- TTL not expired: older values are cached by ISPs and public resolvers.
- Wrong zone edited: you updated DNS at the registrar but the domain is using Cloudflare (or vice versa).
- Nameserver switch in progress: delegation updates can take time across TLD systems.
- Record conflicts: e.g., CNAME on a host that also has A/TXT records.
If updates don’t reflect as expected, a full DNS health check can help confirm your records follow the correct format and standards.
You may also flush your local DNS cache.
What Happens If a Domain Doesn’t Exist
If a domain name is not registered or not present in DNS, servers return an NXDOMAIN response (non-existent domain).
DNS Ports
DNS commonly uses UDP port 53 for standard queries. TCP port 53 is used for larger responses, DNSSEC-heavy answers,
and zone transfers.