Networking: DNS changed but the domain still resolves to the old IP — TTL and resolver caching ("propagation")
You updated a DNS record, but resolvers and devices keep serving the old answer until its TTL expires.
DNS propagationdomain still points to old IPDNS changes not showingdns cache old IP addressDNS record not updating Meaning
There's no real propagation: each resolver caches the old record for the previous TTL. Query the authoritative server directly (dig @ns1.provider.com example.com) to confirm the change, lower the TTL before planned migrations, flush local caches (ipconfig /flushdns, resolvectl flush-caches) and wait out the TTL.
Common causes
- High TTL on the old record
- Resolver or ISP cache
- OS or browser DNS cache
- Changed the record in the wrong zone/nameserver
- Negative caching of an earlier NXDOMAIN
⚡ Quick fix
- Check authoritative:
dig @ns1.provider.com example.com A +short - Flush local DNS caches
- Lower the TTL (300 s) a day before migrations
Detailed fix by platform
Linux
- bash
dig @ns1.provider.com example.com A +noall +answer sudo resolvectl flush-caches
How to diagnose
- Authoritative answer — New IP?
- TTL — Remaining?
- Local cache — Flushed?
🔧 Still not fixed?
Many errors look alike. If the steps above didn’t solve it, one of these is probably what you’re facing:
Similar errors
Most viewed in Networking
- Native VLAN mismatch / wrong VLAN, no connectivity Networking: %CDP-4-NATIVE_VLAN_MISMATCH / device on the wrong VLAN can't reach the gateway
- Port err-disabled (psecure-violation) Networking: %PM-4-ERR_DISABLE: psecure-violation error detected on Gi0/5, putting Gi0/5 in err-disable state
- Rogue DHCP server hands out wrong gateway/DNS Networking: Clients receive the wrong default gateway or DNS server — a rogue DHCP server (often a home router) answers first
Other ways to find it
Where this error sits
Origin: Network. Errors that are often confused with or caused by this one (click to open):
🧠 Still stuck? Analyze your error
Paste the full message, response headers or stack trace — we'll detect the platform and point to the most likely cause.
💬 What worked for others
No tips yet — did something else fix this for you?
Share what worked for you
Tips are checked by an editor before they appear. Links are removed.
Report a correction or suggest an improvement
Last updated 5 Nov 2026