Quick answer: DNS propagation typically takes 15–60 minutes (TTL 3600). With low TTL (300) often 5–15 minutes. If wrong values persist after 48 hours, it's usually a configuration error – not "propagation".
If you landed here: You changed DNS records but browsers, friends or dnschecker.org still show old IP addresses or nameservers.
Realistic times
| TTL before change | Typical wait |
|---|---|
| 300 (5 min) | 5–15 minutes |
| 3600 (1 hr) | 15–60 minutes |
| 86400 (24 hr) | Up to 24–48 hours |
Check propagation
- dnschecker.org – A record globally
dig +trace yourdomain.com A- Nameservers correct? → Nameserver guide
If it "stalls" beyond 48h
Wrong nameservers, typos in A record, Cloudflare proxy showing different IP, conflicting A records. Fix records: Domain won't connect
More: DNS records explained · Troubleshooting hub
Products & ordering: Register a domain · Manage: NexoraHost · My account · nexorahost.com (Frankfurt · 1 Tbit/s DDoS · 99.9% uptime)
Frequently asked questions (FAQ)
How long does DNS propagation normally take?
With TTL 3600 usually 15–60 minutes globally. With TTL 300 often 5–15 minutes. Some ISPs cache up to 24–48 hours.
Why do I still see old DNS after 2 hours?
Local DNS cache (router, PC), high TTL before change or wrong nameservers – resolver still shows old authoritative data.
Can I speed up DNS propagation?
Lower TTL to 300 before changes, wait 24h, then change. After update: check dnschecker.org, flush local DNS cache.