It's over a vpn from Asia to US. I wouldn't worry about that 280ms latency. :) Kind regards, Mark On Feb 9, 2010, at 10:41 PM, Joachim Tingvold wrote:
On 9. feb. 2010, at 15.32, Mark wrote:
Just wondering if anyone is experiencing the same problem with google and openDNS on their end or knows what's going on there with openDNS. The problem just occurred about 20 minutes ago.
Trace is as follows: http://inetpro.org/pastebin/2418
I'd say ~280 ms to your first hop sound's more disturbing then not being able to reach Google (-:
-- Joachim Tingvold joachim@tingvold.com
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
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
participants (2)
-
Joe Abley -
Mark