: Why does flush DNS often fail to work? C:Windowssystem32>ipconfig /flushdns Windows IP Configuration Successfully flushed the DNS Resolver Cache. C:Windowssystem32>ping beautyadmired.com Pinging

@Hamaas447

Most likely the caching issue you are seeing is related to the DNS servers your computer is configured to use. This configuration can be either done manually (to use Google or OpenDNS) or automatically (via DHCP, which uses the DNS servers your ISP recommends). Either way, you can see what your computer is using by following these steps. These servers do cache DNS information for usually hours, sometimes days.

If you already cleared the Windows DNS cache, and you are positive the DNS servers used by your computer uses have already been updated* with new information, then the DNS records are being cached in your browser. Learn how to clear the DNS cache for all the browsers.

*here is a good tool to find out, just input the DNS server your computer is using in the "server" field

Vote Up Vote Down

@Courtney195

The Windows flushdns option only clears your local DNS cache. The next time you request a web address your system will make a new query to your remote DNS servers for the IP address. If your remote DNS servers haven't picked up the new IP address then your system will re-cache the old IP locally.

There's generally nothing you can do to force remote DNS servers to refresh their cache, but you could move away from using your default DNS servers (usually hosted by your ISP) and move to public DNS servers like those hsoted by Google or OpenDNS. These tend to refresh their DNS cache more quickly than many ISPs.

As an additional note for future reference, if you have control over your domain's DNS records then it may be worth setting a lower TTL to suggest they get crawled more frequently, especially if you expect them to be changing in future.

Vote Up Vote Down