Domain name stopped resolving despite seemingly proper config
Posted on 2007-08-07
Today the domain name that for our company stopped working. I have no idea why - a few days ago we renewed out domain, but none of the nameservers should have been changed.
We use bluequartz to administer DNS, and everything looks like it's still set up okay - it's worked fine for the last year or so.
if you try an nslookup, even using the server that acts as the nameserver, you get nothing:
** server can't find avalonglobal.com: SERVFAIL
I did a report through DNSStuff.com, and these were the more interesting points:
FAIL Lame nameservers
ERROR: You have one or more lame nameservers. These are nameservers that do NOT answer authoritatively for your domain. This is bad; for example, these nameservers may never get updated. The following nameservers are lame:
FAIL Missing nameservers 2
ERROR: One or more of the nameservers listed at the parent servers are not listed as NS records at your nameservers. The problem NS records are:
I actually went onto the registrar's site and changed the ns records from ns1.avalonglobal.com to ns1.avalonglobal.net, which actually do resolve at the moment, but it didn't help. (They resolve to the same IP addresses). Even though I've changed the SOA, and the nameservers in my config, nothign seems to have helped...
If anyone can help sort this out, that would be much appreciated.