Solved DNS is not flushing (ipconfig /flushdns not working)?

July 26, 2013 at 13:11:20
Specs: Windows Vista
if dns is not flushing you need to
1. Make host file editable
a. Find your hosts file (%SystemRoot%\system32\drivers\etc\hosts)
b. Uncheck the Read Only attribute

2. Edit your hosts file (in this case by using notepad):
a. Open notepad (right click and run as administrator)
b. Open the hosts file with notepad (make sure to change the type search to All files and not .txt)
c. delete all lines referencing unwanted sites (just leave "127.0.0.1 localhost")
d. save the file

3. Make host file Read Only again
a. Find your hosts file (%SystemRoot%\system32\drivers\etc\hosts)
b. Check the Read Only attribute

4. Flush the dns
a. Run command prompt as administrator to avoid elevation error
b. at C:\Windows\System32> type "ipconfig /flushdns" (space between "ipconfig" and / sign

5. Double check it worked
a. type "ipconfig /displaydns" (it should only show the localhost and no unwanted websites)
b. Close the command prompt
c. ALL DONE!!!


See More: DNS is not flushing (ipconfig /flushdns not working)?

Report •

#1
July 26, 2013 at 13:24:09
✔ Best Answer
Was this intended as a how to? have you considered?

http://www.computing.net/howto/post...

:: mike


Report •

#2
July 26, 2013 at 14:50:38
There must have been a rogue entry in Hosts causing this. My Hosts files have always had plenty of unwanted sites but I've always been able to flushdns. Maybe a virus put something in there.

Always pop back and let us know the outcome - thanks


Report •

#3
July 26, 2013 at 17:28:49
I have this line after the local host ("127.0.0.1 localhost"):

# ::1 localhost (note that it has a double colon in front of the 1)

... should it be there?


Report •

Related Solutions

#4
July 26, 2013 at 18:27:18
Ewen

The hash is rather like a rem in basic (all that follows after it on that line is ignored).
If every line has a hash then Hosts is not in use.

The ::1 localhost loopback entry appears to have been introduced at some stage to allow for newer protocol IPv6, acting in the same way as the 127.0.0.1 localhost entry above it for IPv4. See this discussion:
http://forum.raymond.cc/network/215...

Also see this:
http://www.webopedia.com/DidYouKnow...

...and this:
http://en.wikipedia.org/wiki/Compar...

I've never used the additional ::1 entry personally but simply used 127.0.0.1 localhost as the first entry. However, it seems it "should be there" for XP onwards.

Always pop back and let us know the outcome - thanks


Report •

#5
July 27, 2013 at 17:24:40
Thanks Derek, I've added preferred lines to the localhost before but never noticed the "::". I read your links and all is clear now.

Report •

#6
July 27, 2013 at 17:26:50
Re #5
Looks like we both learned something.

Always pop back and let us know the outcome - thanks


Report •

#7
August 9, 2013 at 10:40:41
Mike,
Thanks. My mistake. I have now placed it in the appropriate forum.

message edited by Anoninc


Report •

Ask Question