DNS propagation explained: why your website isn't loading yet

You just changed your domain's nameservers or DNS records and your site is still not showing up. You are experiencing DNS propagation delay. Here is what is actually happening and what you can do about it.

What is DNS propagation?

When you type a domain name in a browser, your computer does not know where to send the request until it looks up the domain's IP address. That lookup travels through several layers:

DNS propagation is the time it takes for changes to your authoritative nameserver to spread to all the DNS resolvers around the world. Every ISP, every public DNS service (Google 8.8.8.8, Cloudflare 1.1.1.1), and every network has its own cache of DNS records.

Why it takes time: TTL

Every DNS record has a TTL (Time To Live) — a number in seconds that tells resolvers how long to cache the record. Common TTL values:

When a resolver has cached your old record, it will keep using that old value until the TTL expires. This is why propagation takes time — different resolvers cached your record at different times and have different TTLs remaining.

How long does propagation take in India?

Changing an A/CNAME record with a short TTL (300-3600s): 15 minutes to 2 hours in most of India

Changing nameservers: Up to 24–48 hours globally, though most resolvers pick up the change within 4–8 hours

Adding a new record: Usually 15–30 minutes if the parent zone is already resolving

The BSNL, Jio, Airtel, and Vodafone Idea DNS resolvers all behave differently. Some cache aggressively; others check frequently.

Checking propagation status

Use these tools to see what different resolvers around the world currently see:

• whatsmydns.net — shows the record value from dozens of locations simultaneously
• dnschecker.org — similar, good for checking Indian resolver status specifically
• Google's dig tool: https://toolbox.googleapps.com/apps/dig/ — queries Google's own resolvers

From your terminal:

# Check what a specific DNS server sees
nslookup yourdomain.com 8.8.8.8   # Google DNS
nslookup yourdomain.com 1.1.1.1   # Cloudflare DNS
nslookup yourdomain.com 209.244.0.3  # Level3 DNS

# Or use dig
dig yourdomain.com @8.8.8.8
dig yourdomain.com @1.1.1.1

How to reduce propagation time

Lower the TTL before making changes. If you know you are changing nameservers or an A record in 48 hours, drop the TTL to 300 (5 minutes) now. Most resolvers will pick up the change within 5 minutes after the switch.

After the change, restore TTL to a higher value (3600 or 86400) once propagation is complete. A very low TTL on a live site increases DNS query load.

Visiting your new host before propagation completes

You can test your site on the new server before DNS propagates by temporarily editing your computer's hosts file:

On Windows: C:\Windows\System32\drivers\etc\hosts On Mac/Linux: /etc/hosts

Add a line:

123.456.789.0  yourdomain.com

Replace 123.456.789.0 with your new server's IP. Your computer will skip DNS lookup and go directly there. Remember to remove this line after propagation completes.

Specific scenarios and their timelines

Changing nameservers (e.g. pointing to Cloudflare):

• Your registrar must update the NS records at the TLD registry (.com, .in, etc.)
• That change propagates to all root nameservers — typically 24–48 hours
• Nothing will resolve correctly until at least some propagation has occurred

Changing an A record (e.g. new server IP):

• Propagates based on the record's TTL
• If TTL was 86400, expect up to 24 hours in worst case
• If TTL was 300, expect 5–15 minutes

Adding a new subdomain:

• As long as the domain is already resolving, a new subdomain propagates quickly
• Typically 5–30 minutes

MX records (email):

• Propagates on TTL, same as A records
• Email in transit during propagation may bounce or delay — schedule email record changes during off-hours

Why your site loads on mobile but not desktop (or vice versa)

Your phone uses your carrier's (Jio/Airtel/BSNL) DNS resolver, while your laptop uses your WiFi router's DNS, which may use a different upstream resolver. They cache independently.

Force your browser to skip cache:

• Chrome: open DevTools → Network tab → check "Disable cache" → refresh
• Or use Incognito/Private mode (uses a fresh DNS cache)

Flush your local DNS cache:

• Windows: ipconfig /flushdns in Command Prompt
• Mac: sudo killall -HUP mDNSResponder
• Linux: sudo systemctl restart systemd-resolved

Email during nameserver migration

If you are migrating nameservers and you have active email on your domain, the highest-risk period is during propagation — some mail servers may start directing email to your new host's mail configuration before it is ready, or to your old host after you have moved on.

Best practice:

1. Set up and test email on the new host first (verify MX records in the new zone)
2. Lower all TTLs to 300 on the old host
3. Switch nameservers
4. Monitor both old and new mail server logs for 24 hours

VillageHosting's migration team handles this sequence when we migrate your site — email continuity is part of the process.