Author |
Message |
The MAZZTer Death Star
Joined: 25 Sep 2003
|
Posted: Jul 10, 2009 03:58 Post subject: DNS finally gave up |
|
|
It's been completely broken for the past few days for me, I had to hardcode the IP into my hosts file just to get here.
OpenDNS wrote:
Nameserver trace for www.df-21.net:
Looking for who is responsible for root zone and followed m.root-servers.net.
Looking for who is responsible for net and followed k.gtld-servers.net.
Looking for who is responsible for df-21.net and followed ns34a.genericdns.com.
Nameservers for www.df-21.net:
ns34a.genericdns.com
ns34b.genericdns.com
The servers listed are working, but something else might have gone wrong.
nslookup wrote:
C:\WINDOWS\system32\drivers\etc>nslookup www.df-21.net ns34a.genericdns.com
*** Can't find server name for address 75.127.110.46: Server failed
Server: UnKnown
Address: 75.127.110.46
Name: www.df-21.net
Address: 75.127.110.46
C:\WINDOWS\system32\drivers\etc>nslookup www.df-21.net ns34b.genericdns.com
DNS request timed out.
timeout was 2 seconds.
*** Can't find server name for address 67.215.66.132: Timed out
Server: UnKnown
Address: 67.215.66.132
DNS request timed out.
timeout was 2 seconds.
DNS request timed out.
timeout was 2 seconds.
*** Request to UnKnown timed-out
Your webhost's secondary DNS server isn't working, maybe that's it.
_________________ http://www.mzzt.net/ | I am a respectable admin with a respectable sig. |
|
Fenwar Admiral Ackbar
Joined: 15 Sep 2003
|
Posted: Jul 10, 2009 22:06 Post subject: |
|
|
Hmm, I've not had any problem but I get pings of >1s to both of them (which probably explains the DNS lookup timeouts at 2s).
I'll raise a ticket to see if there's anything can be done, but it may just be one of those joys of shared hosting.
|
|
Fenwar Admiral Ackbar
Joined: 15 Sep 2003
|
Posted: Jul 11, 2009 08:05 Post subject: |
|
|
Have been given some new nameservers to use; apparently they changed "some time ago" but I definitely didn't receive any notification about this... Ah well. Hopefully things should improve once the change has propagated.
Thanks for spotting the problem Mega
|
|
The MAZZTer Death Star
Joined: 25 Sep 2003
|
Posted: Jul 13, 2009 15:10 Post subject: |
|
|
Yay I'm gonna remove the hardcoded IP from my HOSTS file now, if the site stops working I'm gonna blame you.
_________________ http://www.mzzt.net/ | I am a respectable admin with a respectable sig. |
|
Fenwar Admiral Ackbar
Joined: 15 Sep 2003
|
Posted: Aug 20, 2009 09:21 Post subject: |
|
|
It's just happened to me (on an office PC that was using OpenDNS) again. However on a separate PC, completely different net connection and not using OpenDNS - works fine.
Basically OpenDNS has a very low timeout and is quick to return its ad page.
If you have the option of going back to the DNS provided by your ISP, or another more tolerant DNS service, I would suggest that.
In the long term it would be nice to change hosts. But I don't have the time or energy to do that at present.
|
|
Fenwar Admiral Ackbar
Joined: 15 Sep 2003
|
Posted: Aug 20, 2009 09:39 Post subject: |
|
|
Have just removed the OpenDNS servers from my list of DNS servers and it's working perfectly again from the work PC (and yes, I flushed the DNS cache before retrying ) Pretty sure it's just the timeout issue.
|
|
The MAZZTer Death Star
Joined: 25 Sep 2003
|
Posted: Aug 20, 2009 21:48 Post subject: |
|
|
I try to avoid Verizon DNS because they've started redirecting non-existent domains to their own search pages. My dad insists he's opted out when he hasn't.
So yeah I've been using OpenDNS. >_> But THEY are doing the same thing too! Augh! But at least it's intermittent as opposed to constant.
Anyways haven't had problems with DF-21 for a bit now.
_________________ http://www.mzzt.net/ | I am a respectable admin with a respectable sig. |
|
|