How to Flush your DNS Cache

If you read the title of this post and you said, "What the heck is DNS Cache?". Let me recommend that you return to looking at Picture of the Day. On the other hand, if you’re interested in what I’m talking about read on:

Today I’ve been waiting for a domain to point to my web server. Furthermore, the sooner this happens the better. Well, as it turns out, a quick check of the domain at DNSreport.com shows that the DNS for this domain has been updated properly. However, when I browse the web via my office cable Internet connection, the domain is still pointing to its old name servers.

In order to confirm that I am experiencing a problem via my cable Internet connection, from a command prompt, I run:

C:\> tracert mydomain.com

The response is:

C:\> Tracing route to mydomain.com [***.***.***.***] over a maximum of 30 hops…

  1. **** Request timed out
  2. **** Request timed out
  3. **** Request timed out
  4. **** Request timed out

and so on and so forth. 

Well, what this seems to indicate is that I can’t browse to mydomain.com because my cable Internet provider’s DNS cache hasn’t been updated. Therefore, I do the following to flush my DNS cache:

  1. Start > Run "cmd"
  2. Do "ipconfig" to see your IP
  3. Do "ipconfig /release" then "ipconfig /renew" 
  4. Do "ipconfig /flushdns"
  5. Now, do "nslookup mydomain.com". 

Now, if the DNS cache was your problem, you should be able to view mydomain.com via your web browser.