DNS propagation is the time it takes for a DNS change to be visible everywhere on the internet - typically minutes to a few hours, at worst 48 hours. The delay doesn't come from your DNS provider pushing changes slowly; it comes from resolvers around the world caching the old answer until its TTL expires.
Why aren't DNS changes instant?
Every DNS answer carries a TTL (time to live) - a number of seconds that recursive resolvers (your ISP's, Google's 8.8.8.8, Cloudflare's 1.1.1.1) may cache it. If your old A record had a TTL of 86400 (24 hours), a resolver that fetched it one minute before your change will keep serving the old IP for the next 23 hours and 59 minutes. Nothing can flush those third-party caches remotely - the TTL is a promise that has to run out.
On the authoritative side, good providers are fast: changes on ice.domains free DNS reach all anycast nameservers within seconds. "Propagation time" is almost entirely cache expiry, not publication.
How long does each kind of change take?
| Change | Governed by | Typical time |
|---|---|---|
| Editing a record (A, MX, TXT etc.) | The old record's TTL | Minutes to hours |
| Adding a brand-new record | Negative-cache TTL of the zone | Usually minutes |
| Changing nameservers | Registry NS TTL (often 48h) | A few hours; up to 48h |
How to make DNS changes propagate faster
- Lower the TTL in advance. At least one old-TTL period before the change, drop the record's TTL to 300s. Example: TTL is 86400 → lower it today, make the real change tomorrow, and caches clear within 5 minutes.
- Keep both endpoints working during the switch. For migrations, run old and new servers in parallel until propagation completes - users on cached answers keep hitting the old server harmlessly.
- Raise the TTL back afterwards (3600s+) to reduce lookup latency and load.
How to check DNS propagation
Query public resolvers directly and compare answers:
dig @8.8.8.8 example.com A +short
dig @1.1.1.1 example.com A +short
dig @9.9.9.9 example.com A +shortWhen they all return the new value, propagation is effectively complete for the vast majority of users. To see what your authoritative servers say (bypassing all caches), query them directly: dig @ns1.ice.domains example.com A +short. Online "propagation checker" tools do the same thing from dozens of locations at once.
My change still isn't visible - what else could it be?
- Local cache: your OS and browser cache DNS too - flush with
ipconfig /flushdns(Windows) or restart the browser. - Wrong zone: if the domain's nameservers point elsewhere, edits in this panel never go live - verify with
dig NS example.com. - Typo in the record name:
wwwvs@is the classic one.