A website or service still goes to the old server after a migration
Your computer and router cache DNS answers. After a server move, your cache may still point at the old address for up to 24 hours.
Try this first
- 1Windows: open command prompt as admin and run "ipconfig /flushdns". macOS: terminal and "sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder" (both are needed since Big Sur, otherwise mDNSResponder keeps serving stale answers).
- 2Fully quit all browsers (not just close the tab). Browsers keep their own DNS cache.
- 3Reboot your router. Sometimes a stale DNS record sits there. Especially on older gear.
- 4Test on your phone over 4G. Works there? Confirms the local cache is the cause.
When to bring us in
For your own server moves, lowering TTL beforehand helps so clients pick up the new address faster. We set that before the switch.
See also
- Wi-Fi drops randomly across the officeFirst rule out whether it is the access points or the internet connection itself. Different fix.
- One room or corner has no or bad Wi-FiNot always "add another AP"; often one is poorly positioned, or there is a metal wall in the way.
- Internet is suddenly slow for everyoneThree suspects: your provider, a colleague soaking the line, or a backup or update kicking in unexpectedly.
None of the above fits?
Describe your situation below. We pass your input plus the steps you already saw to our AI and return tailored next-step advice. If it's too risky to DIY, we'll say so.
Or skip the DIY entirely
Our Managed IT clients do not look these things up. One point of contact, a fixed monthly price, resolved within working hours.