Why my domain shows the wrong site — and why it loads fine for everyone else

You bought a domain, pointed it at your new site, opened it — and there's the old version. Or the registrar's "this domain is parked" page. Or just an error. Meanwhile a colleague messages you: "loads fine for me."
Start with one move that eliminates half the possibilities: open the site on your phone with Wi-Fi off, over mobile data. A different network means a different path to DNS.
- If the phone shows the correct site — your domain is fine. Something on your side is caching.
- If the phone shows the wrong one too — it's the DNS records themselves, or a cache sitting in front of your site.
Here are the three causes, most common first.
Cause 1: a DNS cache remembers the old address
The most common one. Your computer, your router and your ISP remember the DNS answer for as long as the record says — the TTL. Until it expires, nobody asks again where the domain points. The full picture is in what is DNS.
That's why your neighbor already sees the new site and you don't: your caches expire at different times.
How to check. In the terminal:
dig +short your-domain.com
(on Windows, nslookup your-domain.com). Compare the IP you get with the one your host told you to set. If they match, DNS is fine and your problem is further down this list.
It also helps to ask a public resolver directly, bypassing your ISP:
dig +short your-domain.com @8.8.8.8
If the public one returns the new IP while a plain query returns the old one, you've found the culprit.
How to fix. Essentially: wait out the TTL (usually 5 minutes to a few hours) and nudge your own side:
- flush the system DNS cache (
sudo dscacheutil -flushcacheon macOS,ipconfig /flushdnson Windows); - clear the browser cache or open the page in a private window;
- restart the router — it caches too.
For next time: drop the record's TTL to 300 seconds a day before a move, and the switch happens almost instantly.
Cause 2: the records point somewhere else
Second most common — and this one won't fix itself. The usual suspects:
- an old A record is still there. You added the new one but never deleted the previous one. The domain answers with the new address sometimes and the old one other times;
- only the bare domain is configured, not
www(or the reverse).site.comworks,www.site.comshows a parking page; - the record points at the registrar's parking. By default the domain shows "this domain is registered," and that has to go;
- the domain uses someone else's nameservers. You're editing records in the registrar's panel while the domain is actually served by your host's (or Cloudflare's) nameservers — so nobody ever reads your edits.
How to check. See who's actually answering for the domain:
dig +short NS your-domain.com
Edit the records wherever those nameservers live. This is the mistake that costs people days: the changes go into a panel that stopped mattering.
How to fix. Keep exactly one record per name: an A for the root domain and a CNAME (or a second A) for www. Delete the rest. The full walkthrough is in how to buy and connect a domain.
Cause 3: a cache in front of your site serves an old copy
DNS is right, records are clean, and the site is still old — which means there's a layer between the visitor and your server holding a copy of your pages. That's a CDN — Cloudflare, your host's cache, a platform cache like Vercel's.
The tell: the page updates if you open it with ?123 tacked onto the address — that is, as a "new" URL the cache hasn't seen yet.
How to fix. Find the Purge Cache / Clear cache button in the panel and press it. Also check where the CDN is pointing: sometimes the domain has moved but the origin in Cloudflare is still the old server — so visitors are honestly delivered to the old site.
A special case: the browser remembers a redirect
Recognizable symptom: the domain loads correctly in a private window and for everyone else, but your normal window keeps dragging you to the old address.
The cause is a permanent redirect the browser cached for a long time. For the difference between permanent and temporary, see what is a redirect. The cure is clearing site data in your browser settings. And the lesson: until a move is final, don't use a permanent redirect.
How long does a domain take to propagate?
Usually a few minutes to a couple of hours, worst case up to a day. If a day has passed and dig from another network still returns the old address, you're not waiting on propagation — you're looking at the records.
Why does it work for everyone but me?
That's the classic signature of a local cache: system, browser, or router. Testing over mobile data and in a private window settles it in a minute.
The domain shows "not secure" instead of my site
The domain has arrived, but the certificate hasn't been issued for the new name yet. Hosts usually do this automatically within minutes of seeing the correct DNS record — wait and refresh.
The AI Architect 2027 course: step by step from computer basics to your own app and first customers. 543 short lessons on your phone.





