StokeBloke.com

OpenDNS failure?

Friday, November 11th, 2016

Well I spent a few hours yesterday trying to figure out why DNS was failing in some cases.

We use OpenDNS server then fallback to googles.

E.g.
208.67.222.222
208.67.220.220
8.8.8.8

Yesterday nslookup test.uribl.com.multi.uribl.com failed.

After a while I found the following …

OpenDNS server returns server unknown :
nslookup test.uribl.com.multi.uribl.com 208.67.220.220
Server: 208.67.220.220
Address: 208.67.220.220#53

** server can't find test.uribl.com.multi.uribl.com: NXDOMAIN

While google works correctly :
nslookup test.uribl.com.multi.uribl.com 8.8.8.8
Server: 8.8.8.8
Address: 8.8.8.8#53

Non-authoritative answer:
Name: test.uribl.com.multi.uribl.com
Address: 127.0.0.14

I have now switched to use google DNS only. I have no idea why OpenDNS fails for this lookup but not any other.

T Online DNS server is pants

Sunday, August 29th, 2010

For the last few days random DNS lookups have failed and returned t onlines stupid dns error page.   T Online hasnt really been that bad, but I never liked these error pages from the ISP.

http://downforeveryoneorjustme.com/ showed that in every case the website was up.

Today I got a google dns error. I mean google for f**ks sake.