Heads Up :
The post you are writing will appear in a public forum. Please ensure all content is appropriate for public consumption. Review the employee guidelines for the community here.
When I got home tonight the internet was out and I tracked it down to OpenDNS not working. When I did a ping of 208.67.220.220, I got the following:
Reply from 208.67.220.220: bytes=32 time=251ms TTL=49Request timed out.Reply from 208.67.220.220: byt...
We in Sydney Australia are getting very slow performance of OpenDNS and it's been ongoing for the past few weeks. For example:
tracert 208.67.222.222
Tracing route to resolver1.opendns.com [208.67.222.222]over a maximum of 30 hops:
1 <1 ms <1 ms <1 m...
Interesting, I'm getting long ping times again from OpenDNS and here's an interesting section from OpenDNS Diagnostic. Since I'm in Sydney it's strange that the DNS ping is 142ms.
Results for: ping -n 5 rtr1.syd.opendns.com (sydney router)
stdout:
Pi...
FYI, many people in Oz with Optus as their ISP are experiencing this same problem with OpenDNS, so it's not just me. It worked for a while on the 23rd but by yesterday 27th it was broken. Optus seems to be pointing at OpenDNS saying they have no faul...
Given that you see 200ms to 300ms response from DNS servers located in Oz (both OpenDNS and Google have DNS servers located in Oz), then something must be wrong! It's either Optus or the local servers can't handle the traffic. Mine was playing up aga...
As an update, it still does not seem to be working and my ticket has yet to be picked up by OpenDNS. I ran the diagnostic and there are still plenty of timeouts, like the following, which I copied from the diagnostic. What's my best approach now? Sto...
