Free Republic DNS entry seems to be gone

N/A | 04/04/2016 | N/A

[Pox]

I was surfing FR this afternoon and suddenly was unable to access any page on FR and the error stated the server could not be found.

I located the IP address, 209.157.64.200, of the server and then added an entry into my PC's host file and I can now see FR again.

I still do not see a DNS entry for FR, and that is interesting.

[freespirit2012]

I must be the lucky one— have not had a problem at all today, through two computers, though have not tried logging in from phone yet..

[NoCmpromiz]

Is opendns letting the lookup go through now? I’m using opendns and it’s playing Sgt. Schultz, aka ‘I know nothing’

[John W]

NP here all day two locations/providers and various devices. (Xfinity, Metronet)

[Drago]

Try changing her DNS servers from the default Frontier/Verizon ones:

http://www.techsupportalert.com/content/how-find-best-dns-server.htm

[minnesota_bound]

This is what I see if I do not change the company proxy setting.
The site loads but slower.

URL: GET http://www.freerepublic.com/tag/*/index
Category: Politics
Reason: UNKNOWN
Notification: DNS_FAIL

[teletech]

I just tried from my Android Verizon phone and same error.

[snarkpup]

Just went down again (Grand Junction), for about 20 minutes, then came back again.

When it was down, I couldn't ping it either (from a command prompt). I've seen DNSs lose names because of various faults, but going up and down like yo-yos all over the country is a new one on me.

[driftdiver]

Yes, opendns is working great for me. Might depend on which version you went with.

[MadMax, the Grinning Reaper]

TO #36 re you email about DNS, etc. To requote Al Bisiglio (as an Indian) in the movie “Frisco Kid”, when looking at a Jewish torah, said, “I read every word of it and didn’t understand a single one”.

Computerese should be banned on this planet on the penalty of death by keyboard.

[Mr. Rabbit]

I just ran into an DNS problem from Comcast in Albuquerque. Tried to look up the IP on my AWS VM and got 174.137.132.28 which when I put in my hosts file redirected to an obvious malware site with a loud “this is a security alert, please panic and install our crapware” type of spam. (I didn’t LOL) I’ve now put in the 209.157.64.200 IP in my hosts file and am able to get here, but it appears there may be some malicious monkeyshines going on with the DNS. You may want to investigate.

[smokingfrog]

01100011 01101111 01101101 01110000 01110101 01110100 01100101 01110010 01110011 00100000 01100001 01110010 01100101 00100000 01110100 01101000 01100101 00100000 01100110 01110101 01110100 01110101 01110010 01100101

[JudyinCanada]

I can’t get on as of this afternoon except long my phone. That’s in Canada.

[DeltaZulu]

This is due to an outage. A simple fix is to add the IP addres (thanks for posting it) to your Hosts file (Windows: C:\Windows\System32\drivers\etc\hosts, Linux, Apple I assume, /etc/hosts). You need to have admin rights to update it. Add the following entry on line by itself:

209.157.64.200 www.freerepublic.com

[NoCmpromiz]

OK.. I see you’re in FL. I’m in NY. Wonder if a backbone is down. Might explain why you get through but up here in the north the ‘roads’ are closed..

I rarely have had issues with OpenDNS, but right now any lookup that has to access OpenDNS, which would be my two wireless routers, my gateway machine to my LAN, and the DSL modem can’t find FR. Machines on the LAN go through the gateway software which caches the lookup after if gets it, so all of those machines (such as this one) are accessing FR without asking for a lookup externally.

When I checked OpenDNS they did not indicate any server issues except for South Africa.. Are you using enterprise or home OpenDNS?

[John W]

Uodate-Here at home via Safari on iPhone does not work via Xfinity WiFi. Does work going straight with WiFi off via AT&T data.

[dragnet2]

Problem found and traced to a Bombay support site.

.

[Mr. Rabbit]

I suspect a DNS cache poisoning attack or some such that’s trying to swap the 174.xxx.yyy.28 malware IP for freerepublic.com, since that’s what I got on my AWS VM for “host freerepublic.com”. You may get different (or no) results on different parts of the Internet. It’s now back to the correct IP at my AWS VM, but be careful. DON’T put the 174 address in your hosts file — It’s a malware server from what I saw.

[Protect the Bill of Rights]

This afternoon I was able to get FR on my iPad but not my iPhone. Cleared cookies, history & restarted no luck. I looked at my wifi settings. I had changed the DNS server on iPhone to 8.8.8.8. (Google’s ?)

I changed it back to the same setting on iPad- was able to access FR.

(I forget why (troubleshoot maybe) but I had changed the DNS setting on iPhone months ago. )

FR was the only website which would not load. “Server not found”. I had no problems with other sites.

[NewHampshireDuo]

We have two services. A local fixed mobile (RedZone) and satellite (Exede). Cannot access FR via RedZone but Exede is fine.Been this way since late afternoon EST.

[LastDayz]

“I was getting that dumb Time Warner Cable redirect page for about 30 minutes or so.”

I still am but only with Firefox, IE is working fine.

What the hey?