Why DNS Propagation Takes Time

Kecepatan:

Introduction

I’d barely stepped away from my keyboard for five minutes when the monitoring alarm went off. But this time what got me curious was: this error turned out to be more complex than I expected. It’s like trying to walk into your own house but the key’s gone — the door is there, the house is there, but you just can’t get in. That’s exactly what happens with a connection refused error.

So here’s the deal — why does every change take so long to show up? This is one of the errors I encounter most often in the field. From handling dozens of cases, I’ve learned this error has many “faces” — sometimes it’s an easy fix, sometimes it’ll have you pulling your hair out. It’s genuinely tricky.

In this article I’m going to break down this error completely — from causes, symptoms, fix steps, to prevention methods so it doesn’t happen again. Everything based on real experience, not empty theory. Let’s get into it.

Why Doesn’t DNS Change Instantly?

Before diving into the technical explanation, let me give you an analogy so you understand why this happens. Imagine you have a phone contacts list on your phone. Your friend, Pak Budi, changes his number from 08123456789 to 08987654321. You don’t know yet, so when you call Pak Budi, you still use the old number — and of course, the person who picks up isn’t Pak Budi, but some stranger.

You need time to learn the new number. DNS works the same way — the internet has “address books” spread across the entire world, and every change needs time to propagate to all those points. This propagation process is what’s called DNS propagation.

Primary Cause: TTL (Time To Live)

TTL is the “memory duration” of a DNS record. Every time your computer asks “what’s the IP address for domain X?”, the answer comes back with “remember this address for N seconds.” If the TTL is 3600 seconds (1 hour), then for the next hour, your computer won’t re-query that address — it’ll keep using the cached answer.

It’s like you wrote down Pak Budi’s phone number in a notebook. You’ve already written it down, so when you need it, you just open the notebook — no need to call Pak Budi again for confirmation. The problem is, if Pak Budi has changed his number but you’re still using the old notebook, you’ll keep calling the wrong number until your notebook gets updated.

Second Cause: DNS Caching at Multiple Levels

DNS caching doesn’t just happen on your computer. There are many “layers” of caching that need to expire before changes become visible:

Browser cache: Your browser (Chrome, Firefox, Safari) stores DNS lookup results. Usually 1-5 minutes.
OS cache: The operating system has its own DNS cache. On Windows it can be 24 hours, on Linux it usually follows the record’s TTL.
Router cache: Your home or office router also caches DNS. This is an extra delay that’s often forgotten.
ISP DNS resolver: Your internet provider (Telkomsel, IndiHome, etc.) has its own DNS resolver that caches DNS answers. Their TTLs can vary.
Public DNS: If you use Google DNS (8.8.8.8) or Cloudflare (1.1.1.1), they also have their own caching.

So every DNS change has to go through this entire “caching chain” one by one. Think of it like moving house — it’s not just the neighbors who need to be told, but also the postman, delivery couriers, the ride-hail driver who often delivers to your old address, and even the next-door neighbor who sometimes holds your packages. Everyone needs their data updated.

Real-Life Analogy: Moving House

This is my favorite analogy — the easiest to understand. Imagine you’re moving from House A (old address) to House B (new address) in the same city.

DNS change = you’ve already moved to House B. But:

Old friends still remember House A’s address (they’ve cached your old address). They need time to be told your new address.
The postman still sends mail to House A because the database hasn’t been updated. Sometimes the postman is diligent, sometimes lazy — so the timing varies.
Online shopping couriers (Shopee, Tokopedia) still use the old address because they also have their own database that needs updating.
The next-door neighbor who sometimes holds your packages doesn’t know you’ve moved either, so if someone drops off a package at House A, the neighbor gets confused.

The time it takes for everyone to learn your new address = DNS propagation time. If you’re diligent about telling everyone (low TTL), the process is fast. If you’re lazy about it (high TTL), the process is slow.

There’s one more interesting thing. Sometimes you’ve already told your nearby neighbors (local DNS has updated), but neighbors further away (remote DNS) don’t know yet. This is why sometimes you can access a website from one network but not from another — because each network has different “neighbors” and they all update at different times.

DNS Propagation Timeline

Here are the estimated times I typically see in the field for various types of DNS changes:

Type of Change	Minimum Time	Normal Time	Maximum Time
A Record Change	5 minutes	1-4 hours	24-48 hours
CNAME Change	5 minutes	1-4 hours	24-48 hours
MX Record Change	15 minutes	2-8 hours	48-72 hours
NS Record Change	1 hour	4-24 hours	48-72 hours
New domain (purchased today)	15 minutes	1-4 hours	24 hours

Note: the times above are from my experience in production environments. Actual times can be faster or slower depending on the configured TTL, the DNS provider used, and your geographic location.

How to Speed Up DNS Propagation

If you’re in a hurry and don’t want to wait too long, here are some methods I typically use:

1. Lower TTL Before Making Changes

This is the most effective trick. Before making a DNS change, lower the TTL to 300 seconds (5 minutes) and wait for the old TTL to expire. Only then make the actual change. This way, all DNS caches worldwide will “expire” within 5 minutes after the change, not hours.

# Before change: lower TTL to 300 seconds
# Wait for old TTL to expire (e.g. 3600 seconds = 1 hour)
# Then update the IP address
# Low TTL = cache expires fast = propagation fast

It’s like you want to tell a friend about your new phone number, but your friend is the type who diligently writes things down. You tell them: “Hey, my phone number is new, but just remember it for 5 minutes, I’ll tell you again later.” Your friend will write it down, but their memory is short — so when you tell them the correct number, they update immediately. Compare that to if you said “remember this number for 1 year” — your friend will forget that the number has changed.

2. Flush DNS Cache on Your Computer

If you’ve updated DNS but still see the old website in your browser, flush the DNS cache:

# Linux
sudo systemd-resolve --flush-caches
sudo resolvectl flush-caches

# Windows
ipconfig /flushdns

# macOS
sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder

After flushing, open your browser in incognito/private mode. This ensures you’re not affected by browser cache. If it still shows the old version, try restarting the browser.

3. Use a Different Public DNS

Sometimes your ISP’s DNS resolver is slow to update. Try using Google DNS (8.8.8.8) or Cloudflare (1.1.1.1) on your computer to test:

# Linux: edit /etc/resolv.conf
nameserver 8.8.8.8
nameserver 1.1.1.1

# Or test directly with dig
dig @8.8.8.8 yourdomain.com
dig @1.1.1.1 yourdomain.com

It’s like wanting to check Pak Budi’s new address — rather than asking a neighbor who doesn’t know, go straight to Pak Budi himself. The result is more accurate.

4. Verify from Multiple Locations

Use online tools to check whether DNS has propagated from various locations:

whatsmydns.net — check from 30+ locations worldwide
dnschecker.org — another solid alternative
mxtoolbox.com — great for checking MX records and DNS propagation

This helps you confirm whether the change is visible everywhere or if some locations haven’t updated yet.

Pro Tips from Experience

Pro Tip: Always make DNS changes during non-peak traffic hours — ideally midnight or early morning. This way, the impact is minimal and if something goes wrong, you have time to roll back before many users are affected. I once changed an A record at 11 AM — the client’s website was down for 2 hours because propagation wasn’t finished and I updated too quickly. Lesson learned: patience is essential in the DNS world.

Common Mistakes People Make

In the field, I often see the same mistakes repeated. Here are the most common ones:

Updating DNS without lowering TTL first: Many people don’t know this TTL trick. They directly update the IP address while the TTL is still high (3600 or even 86400). The result? Propagation takes hours or even days.
Panicking and updating multiple times: If the first change isn’t visible yet, don’t immediately update again. Wait until propagation completes. Updating multiple times only causes confusion and can make DNS records unstable.
Not verifying from multiple locations: Sometimes the change is visible from your network but not from another network. Always verify from several different locations before declaring “it’s done.”
Forgetting to flush local DNS cache: Often overlooked. You’ve updated DNS on the server, but your computer still has the old cache. Flush it before testing.

FAQ

Q: Why do some people say DNS propagation can take up to 48 hours?

A: That’s true and often happens with NS record changes or new domains registered at certain registrars. Some ISPs and DNS resolvers have very aggressive caching policies with very high TTLs or even hardcoded caching. But for regular A record changes, they’re usually visible within 1-4 hours under normal conditions.

Q: Is there a way to make it take effect instantly without waiting?

A: Unfortunately, there’s no truly instant way for global DNS propagation. What you can do is: (1) lower TTL before changes, (2) flush local DNS cache, (3) use public DNS like Google DNS or Cloudflare for testing, and (4) be patient. DNS is a distributed system designed for consistency, not speed.

Q: Why has it changed on my computer but still shows the old version on my phone?

A: Phones and computers each have their own DNS cache. Flush DNS on both devices. On Android: Settings > Network > Reset Network. On iPhone: Settings > General > Reset > Reset Network Settings. Or just wait a few minutes — phone caches usually expire automatically based on the configured TTL.

Q: Does the DNS provider affect propagation speed?

A: Significantly. DNS providers like Cloudflare, Google Cloud DNS, or AWS Route 53 typically have infrastructure that distributes DNS changes faster than less popular providers. If you frequently need fast changes under urgency, consider using a reputable DNS provider.

Q: How do I know when DNS has fully propagated?

A: Use tools like whatsmydns.net or dnschecker.org. Check from at least 10 different locations. If 80%+ of locations show the new IP, propagation is likely almost complete. For 100% certainty, wait 24 hours.

Conclusion

So here’s the bottom line — DNS propagation isn’t a bug or a problem, it’s a system design that inherently requires time. Just like when you move house, everyone needs time to learn your new address. What you can do is speed up the process by lowering TTL before changes, flushing caches, and using public DNS for verification.

The most important lesson from this article: patience is a skill every engineer must have. DNS propagation takes time, and that’s normal. Don’t panic, don’t update multiple times, and always verify from multiple locations before declaring “done.”

If you’ve had your own experience with slow DNS propagation or have additional tips not mentioned in this article, share them in the comments. We can all learn from each other’s experience, and who knows — your tip might save another engineer from the same problem.

This article is part of the NOC troubleshooting guide series for sysadmins and network engineers. Check out other articles in the DNS category for more DNS troubleshooting guides that might be useful.

Also read: Troubleshooting DNSSEC Validation Failure — Broken Chain of Trust | How to Fix SERVFAIL on All Domain Lookups on DNS Server | Fixing Slow DNS Resolution Causing High TTFB on Asia VPS.