It seems that Google search is broken again. I am getting a completely unfiltered result page, both in IE and Firefox. Is anyone else having this happening recently? Using the last Grypen filtersets.

Thanks!

-Terry

if you use OpenDNS for your DNS servers, then you are not landing on www . google . com ... but landing on www . l . google . com instead...

are you on google . com , or are you on l . google . com ?


if the latter, change your DNS servers and do not use OpenDNS, problem solved, filters back up and running...

You're right. Go figure.

I've been using OpenDNS for a long time now and this only started happening recently. Why does OpenDNS resolve "www.google.com" as "www.l.google.com"?

Any way of getting around this?

only way around it is to NOT use OpenDNS...

i've been using OpenDNS for "years" also, but i refuse to continue when they pull a "stunt" like this!

i don't like this "behind the scenes" type of BS...

It's strange. I use OpenDNS too but I haven't such problem.

Those who have such issue, would you please switch back to OpenDNS and watch the proxomitron log window to see what response code you get when accessing www.google.com?

Normall we should get a 200 code but I doubt you will get a 301/302 redirect, which land you to www.1.google.com.

Preferred DNS = 208.67.222.222 (OpenDNS)
Alternate DNS = 208.67.220.220 (OpenDNS)

Prox Log to access www. google .com
HTTP/1.1 302 Moved Temporarily
lands on www. l. google .com


Preferred DNS = 4.2.2.1 (Level 3/Verizon/GTE/BBN "anycast", thru 4.2.2.6)
Alternate DNS = 4.2.2.2

HTTP/1.1 200 OK
lands where it's supposed to


i've been seing SEVERAL forum posts on various boards discussing users DITCHING OpenDNS because of this "behind the scenes" Google re-direct... seems most have been since Nov. 2007...

i'm leaving my "fix" at just that, DITCHING OpenDNS...
and not tweaking all of my Google filters just to appease such "behind the scenes" BS...