DNS Propagation: Why Changes Take Time & How to Check

What Is DNS Propagation?

DNS propagation is the process by which changes to DNS records spread across the internet's global network of DNS servers. When you update a DNS record — for example, pointing your domain to a new hosting server — that change doesn't appear everywhere instantly. Instead, it takes time for every DNS resolver around the world to pick up the new information.

The reason for this delay is DNS caching. Every DNS record has a Time To Live (TTL) value that tells resolvers how long to cache the record before fetching a fresh copy. Until a cached record expires, resolvers continue serving the old information.

This is why two people in different locations might see different versions of your website simultaneously during a migration — one person's ISP has cached the old record, while another's has already fetched the new one. Propagation is complete when all major resolvers worldwide have updated their caches to reflect the new record.

How Long Does DNS Propagation Take?

The standard answer is "up to 48 hours," but in practice the timeline is more nuanced:

• Within minutes: If you set a low TTL (like 300 seconds) before making changes, many resolvers will update quickly.
• 1–4 hours: Most major ISP resolvers will have updated within this window for typical TTL values.
• Up to 24–48 hours: Some resolvers ignore TTL values and cache records for longer periods, particularly older or less well-maintained infrastructure.

The actual propagation speed depends on several factors:

TTL value: Lower TTL = faster propagation. If you know you're about to make a change, reduce your TTL to 300 seconds (5 minutes) a day or two beforehand. After the migration, you can raise it back to a higher value like 3600 or 86400.

Record type: Some record types propagate faster than others. A records and CNAME records typically propagate at similar speeds, but NS (nameserver) record changes can take longer as they affect the delegation chain.

Resolver behavior: Some resolvers respect TTL values precisely; others cache more aggressively. This is outside your control.

How to Check DNS Propagation Status

While you can't speed up propagation on resolvers outside your control, you can monitor it using global DNS checking tools. These tools query DNS servers in different geographic locations and report what each one sees.

Popular approaches include:

• Command line tools: Use dig or nslookup on Linux/Mac to query specific DNS servers:
  dig @8.8.8.8 example.com A
  This queries Google's DNS server for the A record of example.com.
• Global DNS checkers: Online tools like whatsmydns.net query servers from dozens of locations simultaneously and show a pass/fail map.
• Our WHOIS lookup: Can help verify nameserver assignments and record status.

When checking propagation, look at the IP address returned by each location. If some locations return your old IP and others return the new one, propagation is still in progress. Once all locations return the new IP, propagation is complete.

You can also test DNS from the command line by querying different resolvers:

# Query Google's DNS
dig @8.8.8.8 yourdomain.com

# Query Cloudflare's DNS
dig @1.1.1.1 yourdomain.com

# Query your ISP's default resolver
dig yourdomain.com

Reducing DNS Propagation Time: Pro Techniques

While full global propagation can't be controlled, experienced sysadmins and web developers use these techniques to minimize disruption during DNS changes:

Lower TTL in advance: At least 24–48 hours before a planned DNS change, reduce your record's TTL to 300 seconds (5 minutes). Once the old high TTL expires everywhere, all resolvers are checking frequently. After the migration is complete and confirmed, raise TTL back to 3600 or higher.

Run parallel environments: During migrations, keep the old server running and accepting traffic until propagation is fully complete. Never shut down the old server immediately after updating DNS.

Use a content delivery network (CDN): CDNs with anycast routing can make propagation nearly instantaneous because the CDN's IP addresses are globally distributed and stable.

Flush local caches: After making DNS changes, flush your local DNS cache to see the changes immediately on your own machine without waiting for TTL expiry.

Use Google or Cloudflare for testing: These resolvers update frequently and reliably. If a change is visible via 8.8.8.8, it's likely propagating well globally.

DNS Propagation for Common Scenarios

Different DNS changes have different propagation characteristics. Here's what to expect for common scenarios:

Migrating web hosting (A record change): Update your A record to point to the new server. With a 300-second TTL set in advance, most users will see the new server within 30 minutes. Allow 24 hours for complete global propagation.

Changing nameservers: This is the most significant DNS change and can take longer, as both registrars and resolvers need to update. Allow up to 48 hours. Registrar updates alone can take 12–24 hours.

Email (MX record change): Email is sensitive to propagation delays. During the transition, some mail may still go to your old mail server. Ensure the old server continues to accept mail and forward it during propagation.

SSL certificate validation (TXT record): TXT records for domain verification usually need to propagate before a certificate authority will validate them. With a low TTL, this can happen in minutes; with a high TTL, expect to wait.

After any DNS change, use our DNS leak test to verify your resolver configuration is working correctly.

Frequently Asked Questions