How to check DNS propagation
Confirm a DNS change has taken effect by checking the record from outside your network. Step-by-step, plus why TTL controls the wait.
After you change a DNS record, it does not update everywhere instantly — resolvers cache the old value until it expires. Checking "propagation" means confirming the new value is being served. Here is how.
Why propagation takes time
Every DNS record has a TTL (time-to-live) that tells resolvers how long they may cache it. Until a cached copy’s TTL expires, that resolver keeps serving the old value. So a change propagates over a window roughly equal to the record’s previous TTL — lower TTLs propagate faster.
Checking the current value
Look up the record from outside your own network (and ideally from multiple locations) to see what the world is being served now. If it still shows the old value, its TTL has not expired everywhere yet — wait and re-check.
Step by step
Run a DNS lookup for the changed record from outside your network.
Compare the returned value to the new one you set.
If it still shows the old value, its TTL has not expired — wait the length of the old TTL.
Lower the TTL before a planned change next time so it propagates faster.
Try it now — free, no signup
Use the DNS lookup in your browser. Then, when you need it at scale with an API key and higher limits, grab the full Eveses API.