How propagation really works
DNS doesn’t “spread”: each resolver keeps a cached answer until its TTL expires, then asks again. So a change appears everywhere within the old record’s TTL (often 1 hour, sometimes up to 48).
Reading the results
Green rows agree with the most common answer; amber rows still show a different (usually old) value; red means no record. Global anycast resolvers answer from the location nearest to our server.
Frequently asked questions
Up to the TTL of the old record. If it was 3600, most resolvers update within an hour. Nameserver (NS) changes can take up to 48 hours because TLD servers cache them longer.
Next time, lower the TTL to 300 a day before the change. Once it’s changed, you can only wait out the old TTL (or flush your own computer’s DNS cache).
Some resolvers (for example in China) filter or rate-limit queries from abroad. One timeout usually isn’t a problem.