How To Flush DNS: CMD Is Your Friend

Your computer system is designed to automatically cache IP address and DNS results with an aim of speeding up the results during subsequent requests. Sometimes, the data kept is incorrect and will require to be reset. This is where the need to flush DNS CMD and the resetting of your TCP/IP comes in. TCP/IP resetting is done anytime it gets corrupted.

The procedure involved in flushing DNS and resetting TCP/IP of your computer system

The following steps should be undertaken in the move to flush DNS CMD and reset the TCP/IP address:

  1. Press the window key and search “cmd”.
  2. Click on “Run as administrator”.
  3. From the console prompt, type in “ipconfig /flushdns” to flush DNS. The system will respond with a message indicating successful flushed out DNS resolved cache.
  4. To reset the TCP/IP, type in “nets hint IP reset”.
  5. Reboot the computer system once you are done so as to effect the above changes.

The successful flushing of DNS and resetting of TCP/IP will ensure that your system runs smoothly without delays. Before carrying out the procedure above, you need to know the pros and cons of the procedure.

Pros

  • Speeds up the computer system

DNS flushing and resetting of TCP/IP helps in speeding up your computer commands. Flushing DNS and resetting TCP/IP is aimed to empty and repopulate the DNS settings of your computer, and this, in turn, boosts the speed of your computer.

  • Enhances security of your computer

The cache from the saved DNS and TCP/IP may be a threat to your computer system. The corrupt cache may redirect your command s to a risky website, hence harming your system. Therefore, DNS flushing helps in getting new and correct caches for your computer.

Cons

  • Removes correct and important caches

Flushing DNS and resetting TCP/IP removes all the saved cache. Hence, the user tends to lose both the corrupted cache and the relevant uncorrupted cache.

  • May possibly fail

The above commands may fail to be affected as the DNS cache may continue leading the user to the wrong IP. The problem here is not your computer, but the DNS servers that your computer is using.

Leave a Reply

Your email address will not be published. Required fields are marked *