Quick answer: Typically from a few minutes up to a few hours — governed by the record's TTL. The often-quoted "24–48 hours" is a worst case involving high TTLs and slow ISP resolvers, not the norm. With a TTL of 300 seconds, most of the internet sees your change within minutes.
Overview
When you change a DNS record, nothing is "pushed" around the world. Resolvers simply keep serving their cached copy until its TTL runs out, then fetch the new value. So the visible delay equals: time left on caches (up to the old TTL) plus a little resolver lag.
Before you start
- Check the TTL your records carry right now:
dig A example.com # TTL is the number before "IN A"Step-by-step guide
How to check propagation properly after a change:
- Query several public resolvers directly:
dig +short A example.com @1.1.1.1
dig +short A example.com @8.8.8.8
dig +short A example.com @9.9.9.9- Ask the authoritative server itself (this reflects your edit instantly):
dig +short A example.com @ns1.your-dns-provider.com- If the authoritative answer is correct but your browser still opens the old site, flush the local cache and try a private window.
Common issues
- “Propagation” that never ends: usually the record was edited at a non-authoritative provider — check the domain's NS records.
- Your office still sees the old IP while phones on 4G see the new one: classic resolver caching; it expires on its own.
- Negative caching: if the name did not exist and you just created it, the “does not exist” answer is cached too (per the zone's SOA settings).
When to contact support
Cloud2Y cannot expire third-party resolver caches — nobody can. But if the authoritative servers still hand out an old value hours after your edit, contact your DNS provider; and if the new IP serves the wrong content from our side, open a ticket.
Frequently asked questions
Is 48 hours of DNS propagation normal?
It is the worst case, not the norm. Delay equals the old record's remaining TTL plus resolver quirks — with common TTLs of 5–60 minutes, most users see changes within the hour.
How can I check if my DNS change has propagated?
Query several public resolvers directly, e.g. dig +short A example.com @1.1.1.1 and @8.8.8.8. When they all return the new value, the change has effectively propagated.
Why do I still see the old site after the DNS change?
Your OS or browser cache is holding the old IP. Flush the local DNS cache, use a private window, or test from mobile data to bypass your network's resolver.
Related articles
Ready to get started? Order a VPS at Cloud2Y →
