[122188] in North American Network Operators' Group
Re: Connectivity problems to google via openDNS
daemon@ATHENA.MIT.EDU (Mark)
Tue Feb 9 09:59:29 2010
From: Mark <mark@edgewire.sg>
To: Joe Abley <jabley@hopcount.ca>
In-Reply-To: <4AB1E7D8-1CB0-4A3B-8FE3-3206C4C1F9EB@hopcount.ca>
Date: Tue, 9 Feb 2010 22:52:24 +0800
Cc: nanog@nanog.org
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org
Doh. Didn't realize that. Thanks for the heads up Joe. I'll go take
another look.
Thanks in advance!
Kind regards,
Mark
On Feb 9, 2010, at 10:50 PM, Joe Abley wrote:
>
> On 2010-02-09, at 09:43, Mark wrote:
>
>> It's over a vpn from Asia to US. I wouldn't worry about that 280ms
>> latency. :)
>
> Note that you're not trying to reach google, either.
>
> OpenDNS is returning you addresses for their own proxies. I believe
> they do this as part of some of their content-control services to
> allow you to limit the kind of search queries you (or your users,
> depending on who decided to use OpenDNS) are able to do.
>
> So while the user problem may be "can't reach google" perhaps the
> engineering problem is "can't get response from OpenDNS proxy".
>
>
> Joe
>
