DNS propagation and reverse DNS
Compare answers seen by authoritative name servers and the Google, Cloudflare and Quad9 recursive resolvers. DNS changes do not propagate in sequence from the root down.
On this page
Input
Without expected values, the report only compares whether observations match. When supplied, values are marked as matching your expected old or new values; this does not establish change timing or global propagation. Inputs and results are not placed in URLs or saved as search history, and are cached in a private directory for up to 30 seconds.
Results
Resolver answers may be cached and are displayed separately from direct authoritative answers. Matching results do not mean propagation is complete worldwide. TTL is a remaining-time hint and does not guarantee every cache state.
Regional DNS propagation check
Each region is measured from one probe. The public domain name and record type are sent to Globalping.
Explanation and notes
- The delegation path shows DNS hierarchy, not the order in which changes are distributed.
- Authoritative servers answer for the zone; recursive resolvers show their observations, which may include cached data.
- Response code, elapsed time and TTL are shown per source. Failed lookups are distinct from mismatching values.
- Enter a public IP address to check PTR consistency by looking up whether its reverse hostname resolves back to that address.
Glossary
DNS propagation glossary — full explanations · All glossaries