DNS Propagation Blocked: Why It's Not Propagating

Your DNS change should be visible everywhere but some still see the old value.

DNS propagation is the process by which a record change spreads across resolvers worldwide. Normally, it follows TTL: after cache expiration, resolvers fetch the new value. But sometimes propagation seems blocked: some regions or ISPs still show the old IP days after the change. Causes vary: residual TTL, aggressive ISP cache, NS not updated, or zone problem.

Symptoms of Blocked Propagation

Causes of Blocking

Propagation Diagnosis

  1. Test from multiple locations: use dnschecker.org or whatsmydns.net
  2. Query your NS directly: dig @ns1.yourdns.com example.com to confirm source.
  3. Verify ALL your NS return the same value (synchronized secondaries).
  4. For a specific ISP, ask a user from that ISP to flush their local cache.

Propagation Tracking with MoniTao

MoniTao monitors propagation worldwide:

Ensuring Good Propagation

FAQ - Blocked Propagation

How long does normal propagation take?

Depends on TTL. With 3600s (1h) TTL, 95% of users see change in 1-2h. 100% can take 24-48h.

Why is a specific country blocked?

Local ISPs may have different cache policies. Some countries also have centralized resolvers.

Can I speed up propagation?

Not directly. You can contact a specific ISP to flush their cache, but they rarely accept.

Can propagation fail permanently?

No, all caches eventually expire. If it persists for days, verify NS are correct at registrar level.

Ready to Sleep Soundly?

Start free, no credit card required.