rv45. How it works

DNS PROPAGATION CHECKER

Check DNS propagation around the world.

Look up a record from 33 public resolvers across six continents, and see where your change has arrived.

Points a domain to an IPv4 address. Add an expected value to track a change.

Try

Ready to check 33 locations

Enter a domain above to see what each resolver returns.

Resolvers plotted by the operator’s location. 4 global anycast networks appear in the table below.

Locations

LocationResolverAnswerTTLStatus

Queries are sent from our server directly to each resolver. Each resolver answers from its own cache, so the results show what users of that network currently see. Anycast networks answer from the site closest to our server.

A little DNS clarity.

The essentials behind your results.

What is DNS propagation?

When you change a record, resolvers around the world keep serving the old answer until their cached copy expires. Propagation is the time it takes for every resolver to fetch the new value.

How long does it take?

Usually no longer than the record’s previous TTL, often minutes to a few hours. Nameserver changes can take up to 48 hours because the parent zone’s records have long TTLs.

Why use an expected value?

Without one, RV45 treats the most common answer as the reference. During a change the old value may still be the majority. Enter your new value to count exactly which locations already return it.

What does TTL mean?

Time to live is the remaining cache lifetime. A resolver can continue returning a cached record until that time runs out, then it asks your nameservers again.

Why do some answers differ permanently?

CDNs and load balancers often return different addresses by region on purpose. Some networks also filter or rewrite answers. Differences are not always a propagation problem.