Understanding DNS propagation
Every time you point a domain to a new server, update an MX record or add a TXT entry for email, that change has to travel to thousands of DNS resolvers around the world. Until it does, some visitors reach the new destination while others still land on the old one. That in-between window is what people mean by DNS propagation.
Because resolvers cache answers for the length of a record's TTL, propagation isn't instant. A low TTL set a day before the change means most caches refresh within minutes; a long TTL can keep the old value alive for up to 48 hours. Checking the same record from several regions at once is the simplest way to see how far along you are.
When a global lookup helps
- After moving a site to a new host or IP address.
- When switching email providers and updating MX or SPF records.
- While issuing an SSL certificate that depends on a CAA or TXT record.
- To diagnose why a domain loads for some people but not others.
Run the check, compare the values each location returns, and once they all agree you can be confident the change has fully propagated.