DNS propagation is the time it takes for DNS changes to update across the internet. Change your domain to point to a new server, and different people see different versions until propagation completes.

Typical time: 1-48 hours, usually 4-8 hours in practice.

How It Works

DNS records have a TTL (Time To Live) value. This tells servers how long to cache the record before checking for updates.

Example process:

  1. You change yoursite.com from IP 1.2.3.4 to 5.6.7.8
  2. Your DNS provider updates immediately
  3. But other DNS servers worldwide cached the old IP for the TTL duration
  4. As their cache expires, they fetch the new IP
  5. Gradually, everyone gets the new IP

Why It Takes Time

DNS caching happens at multiple levels:

  • Your ISP's DNS servers (cache for hours)
  • Your router (might cache DNS)
  • Your computer (OS-level DNS cache)
  • Your browser (separate DNS cache)

Each level checks its cache before querying. If cached, uses old value until TTL expires.

How to Check Propagation Status

DNS checker tools:

  • whatsmydns.net (checks from multiple locations worldwide)
  • dnschecker.org
  • Google "DNS propagation checker"

These query DNS servers in different countries. Shows if propagation is complete globally or still in progress.

Command line check:

Windows:

Command
nslookup yoursite.com 8.8.8.8

Mac/Linux:

Command
dig yoursite.com @8.8.8.8

This queries Google's DNS directly, bypassing your local cache.

How to Speed It Up

Before making changes: Lower TTL to 300 seconds (5 minutes) a day before. After propagation, raise it back to 3600 (1 hour) or 86400 (24 hours).

After making changes: You can't speed up global propagation. But you can clear your local caches:

Windows:

Command
ipconfig /flushdns

Mac:

Command
sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder

Linux:

Command
sudo systemd-resolve --flush-caches

Browser: Clear browsing data, restart browser.

Common Issues

  • Still seeing old site after 48 hours: Check if DNS actually changed at your provider, verify nameservers are correct, and note some ISPs ignore TTL and cache longer.
  • Some people see new site, others see old: Normal during propagation. Different DNS servers update at different times.
  • Changed hours ago but you still see old: Clear your local DNS cache. Your computer cached the old value.

Typical Timelines

  • Nameserver changes: 24-48 hours (longest propagation)
  • A record changes: 1-8 hours (depends on old TTL)
  • Low TTL records (300s): 5-30 minutes globally

Bottom Line

DNS propagation is the delay between changing DNS and everyone seeing the change. Caused by caching at multiple levels.

Expect 4-8 hours for most changes, up to 48 hours for nameserver changes.

Lower TTL before making changes to speed it up. Clear local caches to see changes on your device immediately.

Use DNS checker tools to verify global propagation status. If stuck after 48 hours, verify the change actually saved at your DNS provider.