OpenDNS down?

[da.Guvna]

We've had a series of internet 'blackouts' at home this evening. Originally thought it was just general network issues with my ISP, but on further investigation realised that although I couldn't ping domain names, I COULD ping IP addresses.

Changed my routers primary DNS server from OpenDNS to Google DNS, and now all is well again.
Pinging the OpenDNS primary and secondary IPs gets no response.

Anyone else having this?

[BigYoSpeck]

Working fine at my end on Virgin Cable

C:\>time /T
23:41

C:\>ping 208.67.222.222

Pinging 208.67.222.222 with 32 bytes of data:
Reply from 208.67.222.222: bytes=32 time=17ms TTL=53
Reply from 208.67.222.222: bytes=32 time=16ms TTL=53
Reply from 208.67.222.222: bytes=32 time=46ms TTL=53
Reply from 208.67.222.222: bytes=32 time=18ms TTL=53

Ping statistics for 208.67.222.222:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 16ms, Maximum = 46ms, Average = 24ms

C:\>ping 208.67.220.220

Pinging 208.67.220.220 with 32 bytes of data:
Reply from 208.67.220.220: bytes=32 time=19ms TTL=53
Reply from 208.67.220.220: bytes=32 time=18ms TTL=53
Reply from 208.67.220.220: bytes=32 time=18ms TTL=53
Reply from 208.67.220.220: bytes=32 time=17ms TTL=53

Ping statistics for 208.67.220.220:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 17ms, Maximum = 19ms, Average = 18ms

C:\>ping 208.67.220.220

[dave87]

Are you with Be/o2 by any chance?

[jimbouk]

I'm with BE and couldn't get any addresses using openDNS last night. Reset to BE's DNS and it was fine. Are they blocking it or something?

[Lucio]

Nope!

It's an issue on Be/O2/Sky's network at the moment

http://beusergroup.co.uk/index.php?id=615

Add Google DNS servers as a replacement for the time being (8.8.8.8 and 8.8.4.4) as even Be's DNS servers are being flakey

[da.Guvna]

Yep, I'm with Be. Glad it wasn't just me having the issues then!

[MadduckUK]

well that's a bookmark for me, ta. had it twice for about an hour each time last night - thankfully i could just RDP into the work comp and do stuff that way, but a little annoying all the same.

[FatalSaviour]

Wish I'd checked Hexus the other day too now :-), having searched Google's latest 24 hour results for "OpenDNS down" and coming up with nothing.
I switched to Google's DNS too, but it's nice to know that it wasn't OpenDNS throwing a wobbly in the end (I wouldn't have expected it to, but there's always a first!).

[spoon_]

You guys crack me up, what pinging the IP of the DNS server got anything to do with the DNS server actually resolving the names?

[watercooled]

Well, since the OP wasn't getting any pongs back but someone one a different ISP was, shows there's likely a routing problem somewhere between the former ISP and OpenDNS.

[Singh400]

Be's network has been flakey as **** recently. Always used OpenDNS, recently switched to GoogleDNS now though. See how it works out.

[Sputnik]

Only just seen this thread, I had the same problems the other night too and changed to Google's DNS.

Have to agree Singh400, My connection with Be has been a bit flakey lately too when it comes to speed.

[Lucio]

I wonder if they're busy rolling out IPv6 upgrades to their network, they've always been proactive in the past with these kind of things

[BigYoSpeck]

You guys crack me up, what pinging the IP of the DNS server got anything to do with the DNS server actually resolving the names?

Nothing, it just showed they were still on line along with my having no DNS resolving issues meaning the issue would be a specific issue rather than them being down.

[watercooled]

I could only assume this is some sort of upgrade they're doing and something didn't go according to plan, considering their track record.