DNS propagation explained: why your domain change isn't live yet

You changed a DNS record and the site still will not load. That is almost never “propagation” in the mystical sense — it is caching, and it is predictable once you know how it works.

What is actually happening

DNS answers are cached at every step: your operating system, your router, your ISP resolver and public resolvers. Each cache keeps an answer for the record's TTL (time to live).

• Changing a record only changes what authoritative nameservers return.

• Resolvers keep serving the cached answer until the old TTL expires.

• A low TTL before a change means a faster rollout after it.

Why some people see it and others don't

Two visitors can legitimately get different answers while caches expire at different times. That is normal and not a fault.

How to verify a change

Query multiple public resolvers with our free DNS propagation checker. If the new answer appears at most resolvers, the change is live and any remaining delay is a local cache.

Tips to avoid the wait

• Lower your TTL to 300 seconds a day before a planned change.

• Change records during a low-traffic window.

• Remember some ISPs ignore very low TTLs and cache longer.

Once propagation is confirmed, any lingering issue is almost always local caching or a separate configuration problem — not the nameservers.