[Eric Pode of Croydon]

This is a problem with the DNS lookup to FR. As far as I can tell, it is not "blocking" by your ISP or any sort of attack on FR.

Those of you on Windows PC's and who have admin rights can fix this by going to the windows hosts file

look in c:\windows\system32\drivers\etc for a file called "hosts" edit it to add the following line

209.157.64.200 www.freerepublic.com

save and close/restart your browser. You may have to close/restart a second time after logging in to FR, after that should be OK.

[King of Florida]

I don't think so. I'm currently accessing FR on my computer connected to my phone's mobile hotspot (i.e., an AT&T mobile data connection). When I change back to my computer's normal connection -- Comcast -- I get a server not found message when I go to FR. Change back to mobile hotspot, everything's fine.

Something is afoot. I'm not one to ascribe intent, malignant or otherwise, without some proof, but it's odd that every site except FR works fine on Comcast (and that every site including FR works fine on AT&T).

[TexasRepublic]

209.157.64.200 www.freerepublic.com

Adding that entry to the Hosts file is the simplest way to fix this DNS problem. Thanks for reminding me of it!

This trick will work for Mac or Linux too. Just search your computer to locate the Hosts file and then edit that file to include “209.157.64.200 www.freerepublic.com”. I cleared my browser cache, cookies and history, then closed and restarted the browser. No problem!

[dangerdoc]

Thanks.