DNS propagation explained (why changes take time to apply)

When you change DNS settings—like pointing your domain to a new server or updating a mail record—the change doesn't happen instantly worldwide. This delay is called "DNS propagation," and it's one of the most misunderstood parts of domain management.

How DNS works

When someone types your domain into their browser, their computer doesn't ask you directly for the IP address. Instead, it asks a DNS server (often provided by their Internet Service Provider). That DNS server has a cached copy of your domain's DNS information.

Here's the journey:

1. User enters yourdomain.com in their browser.
2. Their ISP's DNS server checks if it has cached information about yourdomain.com.
3. If it has it, the ISP returns the cached result immediately.
4. If it doesn't have it, the ISP queries an authoritative DNS server (yours or your hosting provider's).
5. The authoritative server responds, and the ISP caches the answer.

Why changes take time

When you change a DNS record (like pointing your domain to a new server), the authoritative DNS server is updated immediately. But millions of cached copies exist on DNS servers worldwide.

The TTL (Time To Live) tells all those servers: "Keep this information for X seconds before asking again."

A common TTL is 3600 seconds (1 hour). This means:

• You change your DNS record.
• The authoritative server is updated instantly.
• But a DNS server that cached your old record won't ask for the new one until the TTL expires.
• If 1,000 people access your site from different ISPs, each with a different TTL expiration time, they'll see your old IP until their local cache updates.

This is why propagation takes time. It's not a slow system—it's a deliberate delay to reduce load on DNS servers.

How long does propagation take?

• Best case: A few minutes (if most ISPs have short TTLs)
• Common case: 4–24 hours
• Worst case: Up to 48 hours

Why the variation?

• ISPs set their own TTL values; some are 300 seconds, others are 86400 (24 hours).
• Some servers ignore the TTL and cache longer anyway.
• Some may cache even after TTL expires if load is high.

What happens during propagation

During propagation, you might see inconsistent results:

• Some users reach the new server (their ISP's DNS already updated).
• Other users still reach the old server (their ISP's DNS hasn't updated yet).
• The same user might see different results if they switch networks (home WiFi vs. mobile data uses different ISPs).

This is normal and expected—not a sign of a problem.

How to monitor propagation

Option 1: Online propagation checker

Visit WhatsMyDNS.net or DNSChecker.org:

1. Enter your domain name.
2. The tool queries DNS servers in different locations worldwide.
3. A map shows which servers have the old value and which have the new one.
4. Green = updated, Red = not yet updated.

Example output:

yourdomain.com A record:
✓ Google DNS (8.8.8.8):         192.0.2.1 (new server)
✓ Cloudflare DNS (1.1.1.1):      192.0.2.1 (new server)
✗ Quad9 DNS (9.9.9.9):           192.0.1.5 (old server)
✗ OpenDNS (208.67.222.222):       192.0.1.5 (old server)

Option 2: Command-line check

On Windows (PowerShell):
CODE1

On Mac/Linux:
CODE2

or

nslookup yourdomain.com 8.8.8.8  # Use Google's DNS

Repeat this every 30 minutes to watch the result change as propagation spreads.

Option 3: Your own computer's cache

Clear your local DNS cache and check:

Windows:
CODE4

Mac:
CODE5

Then visit the site in your browser.

What to do while waiting

Don't panic or make repeated changes. Each change restarts the propagation clock. Instead:

1. Verify the change was made correctly in your control panel or registrar account.
2. Use a propagation checker to monitor progress.
3. Wait 24 hours before making any further changes.
4. Test by visiting the site—if you see the correct result, your change is propagating.

If a few hours later most worldwide checkers show green, it's safe to assume the propagation is complete.

Best practices to minimize propagation time

Reduce TTL before a planned change

If you're planning a domain migration or server change:

1. A week before the change, lower your DNS record's TTL to 300 seconds (5 minutes).
2. Wait a day for that low TTL to propagate.
3. Make your DNS change (e.g., point to the new server).
4. Wait 24 hours for the new setting to propagate fully.
5. Increase the TTL back to 3600 or higher to reduce DNS query load.

This speeds up the propagation window significantly.

Keep old servers running during migration

If you're migrating to a new server:

1. Keep your old server online during propagation.
2. Point both domains (old and new nameservers) to your old server initially.
3. When propagation of the new nameserver is mostly complete, switch the domain to the new IP.
4. Leave the old server online for 24+ hours after the switch in case slow DNS caches still point to it.

This ensures no users see downtime.

FAQ

Q: Can I speed up propagation?
A: No—propagation relies on ISPs' DNS cache timers. The only preventive measure is reducing TTL before a planned change.

Q: Why does my site work for me but not others?
A: You're likely on a network that resolved your domain quickly. Others are still cached on the old data. This is normal; wait 24 hours.

Q: What if it's been 48 hours and still not propagated?
A: This is rare but can indicate a configuration error. Check that your registrar's nameservers correctly point to your hosting provider, and that the DNS record exists in your hosting panel. Contact your hosting provider if you're unsure.