Clearing Your IP Cache on your local Computer

Changing your website’s IP address requires patience, as it can take over 48 hours for the change to propagate across the internet. Here’s a concise guide to ensure the new IP is recognized and troubleshoot any issues, especially on your local device.

Step 1: Check Global IP Propagation

To see which IP address the world is associating with your domain:

  • Visit WhatsMyDNS.net.
  • Enter your domain name, select “A” record, and check results from 21 global locations.
  • A few red X’s are normal. If most locations show the new IP, propagation is mostly complete.

Step 2: Fix Local Computer Issues (Windows)

If your computer still shows the old IP, it may be cached locally. Follow these steps:

  1. Open Command Prompt as Administrator:
  • Click the Windows Start button (or search in Windows 10).
  • Type “cmd” in the search bar, right-click “cmd.exe,” and select “Run as administrator.”
Flush DNS Cache:
  • Type “ipconfig /flushdns” (one space after “ipconfig”) and press Enter.
  • You should see: “Successfully flushed the DNS Resolver Cache.”
Check the IP:
  • Type “ping yourdomain.com” (replace with your domain, one space after “ping”) and press Enter.
  • If the displayed IP (e.g., XXX.XXX.XXX.XXX) matches the new IP, the flush worked.
  • If not, try rebooting your computer or clearing your browser cache (note: Firefox has its own DNS cache, so close it before starting).
Restart DNS Client Service (if needed):
  • In the same Command Prompt (as administrator), type “net stop dnscache” and press Enter. Look for: “The DNS Client service was stopped successfully.”
  • Then type “net start dnscache” and press Enter. Look for: “The DNS Client service was started successfully.”
  • Repeat the ping test (Step 3) to check the IP.

Step 3: Fix Router Issues

If the old IP persists and you’re on a local network, your router may have cached it. Try this:

  1. Turn off all devices connected to the router.
  2. Power off your router (if separate from your modem).
  3. Power off your DSL or cable modem (contact your ISP if it has an internal battery). Wait at least 5–10 minutes.
  4. Power on in reverse order: modem (wait for checks to complete), router, then devices.
  5. Repeat the ping test (Step 3) to verify the new IP.

For Mac Users

To reset DNS cache on a Mac, visit Apple’s Support page for instructions specific to your OS version. Check Step 3 first for router-related issues.

FAQ: Common Questions and Issues

Q: Why do I still see the old website after flushing DNS?
A: Your browser cache or router may still be holding the old IP. Clear your browser cache and ensure Firefox is closed before flushing DNS. If the issue persists, follow Step 3 to reset your router.

Q: What if WhatsMyDNS.net shows mostly red X’s?
A: This indicates propagation is still ongoing. Wait a few hours and check again. Full propagation can take up to 48 hours or more in rare cases.

Q: Why does the ping command fail or show no IP?
A: Ensure you typed the domain correctly with no spaces or typos. If it still fails, your network may be blocking ICMP requests, or the domain isn’t resolving. Try accessing the site in a browser or contact your hosting provider.

Q: I don’t have a separate router. What should I do?
A: If your modem and router are combined, power off the modem/router, wait 5–10 minutes, then power it back on. Follow your ISP’s instructions if it has an internal battery.

Q: Can I speed up propagation?
A: Propagation speed depends on DNS servers worldwide. You can’t control it, but ensuring your local device and router are updated (Steps 2 and 3) helps you see the change sooner.

 

Final Notes

  • If the old IP persists after all steps, an upstream router on the internet may still be caching it. This should resolve within hours, or in rare cases, a couple of days.
  • Unfortunately, chat or phone support is not available for this issue.

By following these steps, you can ensure your website’s new IP address is recognized locally and globally with minimal delay.

updated - September 17, 2025

Was this answer helpful? 277 Users Found This Useful (542 Votes)