Loading...

DNS Propagation Checker

Compare DNS records across eight resolver endpoints and check whether they contain your expected value.

Name only, without https:// or a path. Punycode and underscore labels are supported.

Enter one complete record value. A match means the resolver returns this value among its answers. Leave blank to compare answer sets.

Checks use the VuiZ server and selected public resolvers. Regional locations are provider-reported; agreement is not proof of worldwide propagation. DNS.SB endpoint locations
Querying eight DNS resolvers… This may take up to 8 seconds.
Enter a DNS name and record type to compare current answers.
Endpoints returning records
Distinct answer sets

Groups compare only the selected record type; TTL and CNAME alias chains are not included. No-answer and failed endpoints remain in the total.
Resolver / endpoint DNS status Record values / TTL Comparison Query time

Follow VuiZ.Net on Google Search

Add VuiZ.Net as a preferred source on Google to find your favorite tools more easily.

  • Find your tools again
  • Discover new utilities
  • Support VuiZ.Net
Follow

Compare DNS answers after changing a record

After a DNS change, recursive resolvers can keep older answers until their cache entries expire. This checker asks eight fixed DNS-over-HTTPS endpoints for the same name and record type, then groups matching answers so you can spot differences.

The checks run from the VuiZ server through Google Public DNS, Cloudflare and six regional DNS.SB endpoints: New York, London, Frankfurt, Tokyo, Singapore and Sydney. These are snapshots from selected resolvers, not a measurement of every DNS cache or network worldwide.

Key features

  • Nine record types. Check A, AAAA, CNAME, MX, NS, TXT, SOA, CAA and SRV, including names with underscore labels such as _dmarc.example.com.
  • Answer groups. Resolvers returning the same set of selected record values share a group. Comparison ignores TTL, answer order and duplicates, normalizes IP addresses and hostname case, and joins quoted TXT chunks.
  • Expected value matching. Optionally enter one complete record value. Each resolver is marked according to whether its answer set contains that value; this does not require the entire set to contain only that record.
  • Individual resolver outcomes. View records, TTLs in seconds, CNAME aliases, DNS error codes and HTTP query durations. A failed endpoint does not hide results from the other endpoints.

How to check DNS propagation

Compare the current responses for the exact DNS name you changed.

  1. Enter the DNS name. Enter a domain or subdomain without a URL scheme, port or path. For internationalized domains, use the Punycode name. Use Sample to fill example.com.
  2. Select the record and expected value. Choose a record type. Optionally enter one expected record value, following the placeholder; for MX or SRV include the numeric fields.
  3. Run the check. Click Check DNS and wait for the eight resolver queries. Review answer groups, expected matches, TTLs and errors in the results table.
  4. Save or check again. Copy or download JSON to retain the timestamp and individual responses. Click Check DNS again for a new snapshot, allowing for resolver cache expiry and the request limit.

Usage tips

  • Query the exact name: an apex domain, www subdomain and _dmarc label can have different records. A missing record is different from an NXDOMAIN response.
  • CDNs, GeoDNS and load balancing can intentionally return different IP sets. A larger answer group is not proof that its values are the correct ones.
  • TTL is the lifetime reported for a returned record, not a countdown to global propagation. Lowering a TTL now does not erase an older answer already cached elsewhere.
  • Queries send the DNS name to VuiZ and the listed resolver operators. Expected values are used by VuiZ for comparison and are not forwarded to the resolvers.

Frequently asked questions

No. Agreement only covers the endpoints that returned records in this check. Your ISP, device, browser, other resolver nodes and authoritative nameservers can still have different data. All eight endpoints must return matching records for the all-agree message.
The six city labels are the regional DNS.SB endpoints published by that provider. Google and Cloudflare use anycast and are shown without a fixed city. Queries originate from the VuiZ server, and network routing or provider changes can affect the actual serving infrastructure.
NXDOMAIN means the resolver reports that the name does not exist. No records means a successful DNS response contains no answers of the selected type, possibly with a CNAME alias. SERVFAIL can result from DNSSEC validation or upstream resolution failure. None of these outcomes counts as an answer match.
Enter one value, such as an IPv4 address, a CNAME target or an MX preference plus hostname. Matching normalizes IP notation, hostname case and trailing dots. TXT can be entered as plain text or quoted chunks; its text remains case-sensitive. CAA values also remain case-sensitive. A match means at least one returned record has that value.
Checks are manual and limited to six requests per minute per client. Each request queries eight fixed endpoints with an eight-second timeout. Custom resolver URLs are not accepted. VuiZ does not cache the result, but recursive DNS caches and provider availability still affect each response.