Skip to content

How to clear your DNS cache (Flush DNS)

G19th January 2013

C2 Comments

Tbrowser, domains, Windows

If you are encountering a high number of HTML Error 404 codes, you may need to flush your DNS cache. Here are instructions for clearing the DNS cache.

Most operating systems and DNS clients will automatically cache IP addresses and other DNS results in order to speed up subsequent requests to the same hostname.  Your DNS cache stores the locations (IP addresses) of web pages you have recently viewed. If the location of the page changes before the entry in your DNS cache is updated, you will be unable to access the page.

If you are encountering a high number of HTML Error 404 codes, you may need to flush your DNS cache. Once you clear your DNS cache, your computer will query nameservers for the new DNS information rather than relying on old information stored on your computer.

Here is how to flush your DNS resolver cache. You may need administrator rights to perform this action.

Step 1

In Windows Vista/7/8, go to the start button and type “cmd” in the Search panel, then press Enter. Otherwise navigate via Start > All Programs > Accessories > Command Prompt.

dnsflush-01

In Windows 98/NT/2000/XP, navigate via Start > Run, press “cmd.exe” and press OK.

Step 2

In the command prompt, type “ipconfig /flushdns”

dnsflush-02

Step 3

You will receive a message confirming that the DNS cache has been flushed:

dnsflush-03

The resolver cache has been cleared.

Step 4

Close the command prompt.

Mac and Linux:

Instructions for completing the same procedure on Macintosh and Linux systems can be found here.

   

Comments:

2 responses to “How to clear your DNS cache (Flush DNS)”

  • Written by Kate on 28 April 2013:

    Isn’t it also recommended that the user clear their browser’s cache after flushing their DNS using the command prompt?

    • Written by Adam Dimech on 12 May 2013:

      Hello Kate,

      That is correct. Good advice.

Have your say:

The following HTML is permitted:
<a href="" title=""> <b> <blockquote cite=""> <code> <em> <i> <q cite=""> <strike> <strong>

Comments will be published subject to the Editorial Policy.