OpenDNS blocking google?

[feralwolf]

Hello, I just got done configuring my amahi server, and the most of the features are working out great for me.

I am having one problem, however. As soon as I disabled DHCP on my router and reset my network settings on my client computer, I found that I am not able to access google. I can ping it successfully, however as long as I am pulling an IP from my amahi server, I get a "connection reset" error whenever I try to go to google. As soon as I disconnect my amahi server and re-enable my router's DHCP, I am able to pull it up just fine. I have researched thsi issue online and saw that some people have had similar issues with OpenDNS, but didnt find any thing conclusive. My amahi installation is fresh, so there shouldn't be anything in my configs aside from the defaults. Is there something I'm missing?

Thanks for any help.

[cpg]

WOW. that seems bad. real bad. i have heard of spats between opendns and google, however, it's not clear they could get away with that.

can you double check?

cause if that is the case we need to find alternatives!!

[lou1z]

never had it block google but i noticed it had started to block some ebay pages (feedback) claiming they were phising sites. i would imagine that if it blocks google with the user just using opendns as a dns server and not using their filtering (via their control panel), then there is something seriously wrong somewhere.
generally, it would show a "blocked" message page when a site has been blocked along with the reason.

[moredruid]

can't say. I've modified my DNS servers to those of my ISP due to latency issues with the OpenDNS servers. Those work fine although they will block some domains (registered as illegal sites in NL with explicit content with minors)... never seen a "blocked" message tho

[cpg]

ok, in case it helps someone, here is a quick & dirty script to get the DNS changed

Code: Select all

wget http://dl.getdropbox.com/u/364883/Amahi/hda-change-dns chmod 755 hda-change-dns ./hda-change-dns IPDNS1 IPDNS2

where the two IPs of the new servers are specified in IPDNS1 and IPDNS2.

it will get into the next release.

[moredruid]

nice work cpg. It's good to have this done through a script for now to reduce the margin of error.

[feralwolf]

Thanks cpg, I'll try that script and see if it works out. Its a bit odd how this is happening though, I'll add some details in case someone else happens to be experiencing the same issue or can think of anything i might have missed.

My main client PC is running a RC of windows 7 (build 7100), this is the one that was unable to access google at all while my amahi was up. Flushing the DNS cache didn't help.
I also have a Mackbook( OS X 10.6) and a laptop(Win XP) who also had intermittent issues accessing google's webpages and search services(toolbars, etc...). On my mackbook it seemed like all i had to do was reset my network settings and refresh the page a few times and it loaded. I have yet to test on XP myself, but my roomate said he was experiencing the same issues.

I will note that when I point my Windows 7 machine's default DNS to a opendns server (208.67.222.222) the problem continued, even while my amahi hda was taken offline and I was pulling my IP from my home router. Soo... it seems that its not anything related to the amahi server specifically, just the OpenDNS.
I suppose it is entirely possible that this has something to do with the way the DNS is being cached, or some bug with the version of windows 7 I am running, it is only a release client after all.

I'll see how it effects my XP laptop and get back to you.

Edit:
During my initial testing I also went into my OpenDNS configuration settings on their website and set it so nothing was blocked, even phishing sites.