What is DNS propagation?

DNS propagation is the period while DNS caches around the internet update after a record change.

How long does DNS propagation take?

It depends on TTL, resolver caching and previous records. Some changes appear within minutes, while others may take hours.

Can I force DNS propagation?

You cannot force every resolver to update instantly, but lowering TTL before a planned change can reduce waiting time.

DNS Guide

DNS propagation explained

DNS propagation is the waiting period while resolvers and caches around the internet learn about a domain record change.

What DNS propagation really means

When you change a domain record, the update is made at your authoritative DNS provider. Visitors, however, usually do not ask the authoritative nameserver directly. Their browser, router, ISP resolver, public resolver, operating system and application may all cache DNS answers. Propagation is the practical delay caused by those caches.

The most important value is TTL, or time to live. TTL tells resolvers how long they may keep an answer before asking again. If an old A record had a TTL of 3600 seconds, some users may continue seeing the old IP for up to about an hour after the change. If a resolver ignores TTL, has stale cache, or was queried just before the change, the delay can feel longer.

Common propagation symptoms

Some users see old siteResolvers still cache the previous A or AAAA record.Wait for TTL and verify authoritative records.

Email still failsMX, SPF, DKIM or DMARC records may be stale.Check TXT and MX separately.

www works, root failsRoot and subdomain records are separate.Check both names explicitly.

IPv6 fails onlyAAAA record may point to an unready server.Compare A and AAAA results.

Use DNS Lookup to check the current visible records. If you recently migrated hosting, compare the returned IP with the new server public IP and review both IPv4 and IPv6 records.

How to reduce DNS change pain

Lower TTL before a planned migration, ideally a day before the change.
Confirm the new server is ready before changing records.
Change one layer at a time when possible: DNS, HTTPS, redirects, email records.
Keep the old server available during the transition window.
After the change, test DNS, port 443 and HTTP headers together.

Propagation is not a sign that DNS is broken. It is a normal consequence of caching. The goal is to plan changes so cached records expire quickly and old infrastructure continues working until traffic moves.

FAQ

Why does my computer still see the old IP?

Your operating system, browser, router or DNS resolver may have cached the previous answer.

Does changing nameservers take longer?

Nameserver changes can take longer because parent-zone delegation and resolver caches are involved.

Should TTL always be low?

No. Low TTL can help during migrations, but higher TTL can reduce DNS traffic and improve cache efficiency for stable records.

Why do different DNS tools show different results?

They may query different resolvers or locations, and those resolvers may have different cache states.

Can DNS propagation affect SEO?

Short, well-managed changes are usually fine. Long outages, broken HTTPS or inconsistent redirects are more concerning.

DNS propagation explained

What DNS propagation really means

Common propagation symptoms

How to reduce DNS change pain

FAQ

Related guides