DNS Propagation Checker
Compare DNS records across eight resolver endpoints and check whether they contain your expected value.
| Resolver / endpoint | DNS status | Record values / TTL | Comparison | Query time |
|---|
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.
- 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.
- 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.
- 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.
- 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.