DNS Propagation

How to use this check

Choose a hostname, record type and optional expected value to compare what the public resolver path returns now.

NetProbe runs regional DNS-over-HTTPS checks with locality hints, returned values and minimum TTL.

How to interpret the result

Different answers can be normal while TTLs expire; the key signal is whether authoritative and public resolver answers converge.

Example

After changing an A record, one resolver may still show the old IP until its previous TTL expires.

Common issues and next steps

Propagation confusion often comes from stale local cache, wrong authoritative zone or checking the wrong record type.

Flush local cache, verify the authoritative nameservers and compare again after the longest relevant TTL.

Methodology and limits

Current public coverage uses regional resolver hints, so read it with authoritative DNS and TTL timing rather than as a physical server guarantee for every city.