What is DNS propagation and why does it take time?
The window of time required for authoritative DNS zone changes to distribute and refresh across recursive caching resolvers worldwide.
Micro-Technology Solutions
Check global DNS record propagation in real time across resolvers in 20+ countries with interactive map and latency telemetry.
Enter a domain name above and press 'Search' to generate the real-time server propagation audit and telemetry.
When you update a DNS record (such as an IP in an A record or mail servers in an MX record), the change is not immediately reflected across every client worldwide. Internet Service Providers (ISPs) and resolver nodes in each country cache previous answers for the duration defined by the TTL (Time-To-Live). This tool queries resolvers in 20+ strategic worldwide locations across the Americas, Europe, Asia, Africa, and Oceania to show you exactly what each region sees.
Client-side actionable solutions versus authoritative server diagnostics.
Your computer or router still holds the old IP address in local cache. Run `ipconfig /flushdns` in Windows CMD or reboot your router.
The OS local resolver cache holds entries until the internal TTL countdown hits zero, regardless of upstream authoritative changes.
This is expected during the first hours of migration. Allow time for the previous TTL to expire worldwide.
Regional ISPs in different continents refresh their recursive caches asynchronously as users request the domain.
Only 13 IP addresses exist for global root DNS servers (A through M) due to the original 512-byte UDP packet size limit.
The first domain name registered in history was `symbolics.com` on March 15, 1985.
Lowering TTL to 300 seconds 24h before a server migration ensures worldwide propagation completes in just minutes.
Learn the fundamental concepts, protocols, and technical terminology of this tool.
The window of time required for authoritative DNS zone changes to distribute and refresh across recursive caching resolvers worldwide.
An expiration value in seconds instructing intermediate resolvers how long a DNS response may remain cached before querying authoritative servers again.
A routing scheme where multiple geographically dispersed server nodes announce the same IP address, directing queries to the topographically closest PoP.
An upstream resolving node that navigates through Root, TLD, and Authoritative hierarchies to deliver the final resolved record to client machines.