DNS Propagation — Why DNS Changes Don't Work Immediately

You switched hosting, updated an A record, or transferred a domain — but the site still opens from the old server. Sound familiar? This is DNS propagation — the process of distributing DNS changes across servers worldwide. In this article, we'll explain how it works and what you can do to avoid waiting two days.

What Is DNS Propagation

DNS propagation is the time it takes for DNS record changes to spread across all DNS servers on the internet. When you change a record at your registrar, the update doesn't happen instantly — it gradually propagates through the hierarchical DNS system.

Typical propagation times:

• A / AAAA records — 5 minutes to 48 hours
• MX records — 1 to 48 hours
• NS records — 24 to 72 hours
• TXT records — 5 minutes to 24 hours
• CNAME records — 5 minutes to 24 hours

How DNS Works and Why Propagation Isn't Instant

DNS Hierarchy

The DNS system works as a chain:

1. Root servers (13 groups) — know where to find top-level DNS zones (.com, .ru, .io)
2. TLD servers — know the authoritative NS servers for each domain in the zone
3. Authoritative NS servers — store the actual DNS records for your domain
4. Recursive resolvers (ISP DNS servers, 8.8.8.8, 1.1.1.1) — cache results and serve them to users

The Role of TTL (Time to Live)

Each DNS record has a TTL — time to live in seconds. This value tells recursive servers how long to cache the record. Until the TTL expires, the server returns the cached value without querying the authoritative server.

example.com.  3600  IN  A  93.184.216.34
;             ^^^^
;             TTL = 3600 seconds = 1 hour

Typical TTL values:

How to Check DNS Propagation

Using enterno.io

The most convenient method is to use enterno.io DNS Lookup. Enter the domain name, and the tool will show the current DNS records as seen by the server. Compare the result with what you configured at your registrar.

Via Command Line

Check the record on different DNS servers:

# Google DNS
dig @8.8.8.8 example.com A

# Cloudflare DNS
dig @1.1.1.1 example.com A

# Authoritative server
dig @ns1.registrar.com example.com A

# Short output
dig +short example.com A

If the authoritative server returns the new IP but Google DNS returns the old one, propagation hasn't completed yet.

On Windows

nslookup example.com 8.8.8.8
nslookup example.com 1.1.1.1

How to Speed Up DNS Propagation

1. Lower TTL in Advance

The key technique: 24–48 hours before the planned change, reduce the record's TTL to 300 seconds (5 minutes). Wait for the old TTL to expire, then make your changes. After the migration is complete, restore the TTL to the standard value.

# 48 hours before migration
example.com.  300  IN  A  93.184.216.34

# After migration (once you've confirmed everything works)
example.com.  3600  IN  A  NEW.IP.ADDRESS

2. Flush Local DNS Cache

Your computer caches DNS responses. Clear the cache:

# Windows
ipconfig /flushdns

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

# Linux
sudo systemd-resolve --flush-caches

3. Switch DNS Server

If your ISP's DNS is slow to update, switch to Google (8.8.8.8) or Cloudflare (1.1.1.1) — they refresh their cache faster.

4. Use Cloudflare Proxy

If the domain is connected to Cloudflare, A record changes take effect instantly since traffic goes through Cloudflare's servers, not directly.

Common Problems During DNS Migration

• Didn't wait for old TTL to expire — the most common mistake. If TTL was 86400 (24 hours), some users will see the old address for another day even after the change
• Forgot the www record — updated the A record for example.com but not for www.example.com
• Didn't account for CNAME — if www points to a CNAME, verify that the target record is also updated
• NS delegation issues — changing NS servers takes the longest to propagate
• Negative caching — if the DNS record was temporarily missing, recursive servers cache that fact (negative caching)

DNS Propagation and Email

Be especially careful when changing MX records. During propagation, some emails may go to the old server while others go to the new one. Recommendations:

• Don't decommission the old mail server until propagation is fully complete
• Set up forwarding from the old server to the new one
• Lower the TTL for MX records in advance
• Monitor delivery of test emails

Summary

DNS propagation is an inevitable process, but it can be controlled. Key rules:

1. Plan your migration in advance
2. Lower TTL 48 hours before changes
3. Check propagation using enterno.io DNS Lookup
4. Don't remove old records until the process is fully complete
5. Use multiple DNS servers for verification