
This is a placeholder text
Group text

by Kalibeck on 08 July 2012 - 16:07
by beetree on 08 July 2012 - 17:07

by Judy P on 08 July 2012 - 18:07

by BabyEagle4U on 09 July 2012 - 02:07
1. Open up the Command line (Windows users, go into start, Search "command" and click on the program to open up the Command prompt, Mac users can check their DNS server by going into "System Preferences" search for the "Network" icon and check there).
2. type in "ipconfig /all" make sure there is a space between ipconfig and /all.
3. Scroll up to find where it says "DNS Servers".
4. Check the number given against these FBI-identified rogue server addresses:
85.255.112.0 through 85.255.127.255
67.210.0.0 through 67.210.15.255
93.188.160.0 through 93.188.167.255
77.67.83.0 through 77.67.83.255
213.109.64.0 through 213.109.79.255
64.28.176.0 through 64.28.191.255

by Kalibeck on 09 July 2012 - 03:07

by yellowrose of Texas on 09 July 2012 - 18:07
SINCE when do we trust a government site???
lol
YR

by yellowrose of Texas on 09 July 2012 - 18:07
I don't KNOW about TOMORROW but I know who HOLDS MY HAND>>
YR

by Keith Grossman on 09 July 2012 - 19:07
This is a day late, I know, but if you are on a home network, you need to check your router, not your individual machine. Most default to "obtain DNS sever address automatically from ISP" and if your router says that, you're fine. It's only if the router has a specific IP address in it and it's one that falls within the published ranges that there would be an issue.
I was pretty sure I wouldn't have any issues...I built 'Watson Jr.' and he's a hoss...and well protected.

by Kalibeck on 10 July 2012 - 05:07
Thanks Keith.....good to know.....so I guess most of us are OK then!
Jan I'm glad you're good to go, too! I only found out about this from my work on Saturday, I just didn't want any of my friends to suffer from this.....
jackie harris
Contact information Disclaimer Privacy Statement Copyright Information Terms of Service Cookie policy ↑ Back to top