DNS Propagation: What It Is and How to Check It

DNS propagation is the process by which updated DNS records are distributed across all DNS servers worldwide. When you change a DNS record — such as updating an A record to point to a new server, changing nameservers, or modifying MX records — these changes don't take effect instantly everywhere. Instead, they gradually spread across the global network of DNS resolvers.

During propagation, some users may see the old DNS records while others see the new ones, depending on which DNS server their device queries. This is completely normal and expected behavior.

DNS propagation takes time because of caching. Here's how the DNS caching system works:

When a DNS resolver looks up a domain for the first time, it queries the authoritative nameserver and caches the result. The cache duration is controlled by the TTL (Time to Live) value set on each DNS record. Until that TTL expires, the resolver serves the cached (old) result instead of querying the authoritative server again.

Since there are millions of DNS resolvers worldwide, each with its own cache, and each having cached the record at different times, the old records expire at different times across the internet. This staggered expiration is what we call "propagation."

Factors that affect propagation time:

• TTL value: Higher TTL = longer propagation. A record with a 24-hour TTL may take up to 24 hours to propagate fully.
• ISP DNS caching: Some ISPs ignore TTL values and cache records for longer periods.
• Local DNS caches: Your operating system and browser also cache DNS records.
• Multiple levels of caching: The request may pass through several DNS resolvers, each with its own cache.

In most cases, DNS propagation takes between 15 minutes and 48 hours, though the majority of users will see changes within a few hours.

Typical propagation times by change type:

• A/AAAA record changes: 1–24 hours (depends on the previous TTL)
• MX record changes: 1–24 hours
• Nameserver changes: 24–48 hours (registries have their own cache)
• New domain registration: Usually under 12 hours
• TXT record changes: 1–24 hours

If you're planning a migration or DNS change, you can reduce the propagation window by lowering the TTL of the affected records to a short value (like 300 seconds / 5 minutes) at least 24–48 hours before making the actual change. After the change has propagated, raise the TTL back to a longer value to reduce DNS query load.

Use LookMyIP's DNS Propagation Checker at lookmyip.com/propagation. It queries DNS servers across multiple global locations simultaneously and shows you whether each server is returning the old or new records. This gives you a real-time view of propagation progress.

What to look for:

• If all servers show the same (new) value, propagation is complete.
• If some show the old value and some show the new value, propagation is still in progress.
• If all servers still show the old value, the change may not have been applied to your authoritative nameservers yet — double-check with your DNS provider.

Lower TTL before making changes: Set the TTL to 300 seconds (5 minutes) at least 24–48 hours before you plan to make the DNS change. This ensures resolvers are already using a short cache period when the change happens.

Flush your local DNS cache: After making changes, clear your local cache to see the new records immediately on your own machine:

• Windows: ipconfig /flushdns
• macOS: sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder
• Chrome: Visit chrome://net-internals/#dns and click "Clear host cache"

Use a different DNS resolver: If your ISP's DNS server is slow to update, try switching to Google DNS (8.8.8.8), Cloudflare DNS (1.1.1.1), or OpenDNS (208.67.222.222).

Don't make multiple changes during propagation: Wait for one change to fully propagate before making another. Stacking changes during propagation can lead to inconsistent states.