Rollout and caching

Verify a change has propagated

Run the same query across several public resolvers and watch the agree/differ verdict and per-resolver latency.

When to use it

Use this when

  • You just changed a record and need to know which resolvers still serve the old value.
  • Users report stale results and you suspect resolver caching or a slow rollout.

Steps

Do this

  1. Enter the host and typeOpen Propagation, type the host, and pick the record type you changed.
  2. Compare resolversdnsbin queries each public resolver and shows the data plus response latency side by side.
  3. Read the verdictA single agree/differ banner tells you whether every resolver returned the same answer yet.

Examples

Copyable commands

REST
curl 'https://dnsbin.ca/api/v1/propagation?name=example.com&type=A'
REST — streamed (SSE)
curl -N -H 'Accept: text/event-stream' \
  'https://dnsbin.ca/api/v1/propagation?name=example.com&type=A'

Operational notes

Keep in mind

  • Differences almost always mean caching and TTL, not a misconfiguration — wait out the previous record’s TTL and re-check.
  • Resolvers may answer from different anycast nodes, so latency is indicative, not a benchmark.