DNS Problems - Ticket #937497


#1

Hate to be one of those people that uses a forum to speed up support, but could someone take a look at ticket #937497 (just broke the 33 hour mark)? It’s a follow-up to ticket #936849 (which broke 26 hours). Both of those also refer to #936005 & #3517551.

It seems like a simple DNS problem, but something must be getting overlooked. I use NS1/NS2/NS3.dreamhost.com for all domains (full, mirrored, subs), but a dig on some of them pulls up newdream.net info. Any domain that somehow shows newdream info also has problems and pulls up multiple failure & warning messages at dnsreport.com.

I’m not an expert, but it seems like replacing newdream ns with dreamhost ns in the dns zones would be the fix.

Below are some of the errors that dnsreport.com pulls up. Plus, other errors come and go, like not connecting to the mail server, or no response from name servers.

I know you guys are busy counting money, fighting off girls, waxing Lamborghinis, and signing autographs… but I’d greatly appreciate the help. :smiley:

Thanks!

  • Mike Seiler

WARNING. The parent servers (I checked with TLD1.ULTRADNS.NET.) are
not providing glue for all your nameservers. This means that they are
supplying the NS records (host.example.com), but not supplying the A
records (192.0.2.53), which can cause slightly slower connections, and
may cause incompatibilities with some non-RFC-compliant programs. This
is perfectly acceptable behavior per the RFCs. This will usually occur
if your DNS servers are not in the same TLD as your domain (for
example, a DNS server of “ns1.example.org” for the domain
"example.com"). In this case, you can speed up the connections
slightly by having NS records that are in the same TLD as your domain.


And when that happens, it also gives a warning that it can’t verify that the nameservers are on separate class C’s.


Missing (stealth) nameservers
FAIL: You have one or more missing (stealth) nameservers. The following
nameserver(s) are listed (at your nameservers) as nameservers for your
domain, but are not listed at the the parent nameservers (therefore,
they may or may not get used, depending on whether your DNS servers
return them in the authority section for other requests, per RFC2181
5.4.1). You need to make sure that these stealth nameservers are working;
if they are not responding, you may have serious problems! The DNS Report
will not query these servers, so you need to be very careful that they
are working properly.

ns2.newdream.net.
ns3.newdream.net.
ns.newdream.net.

This is listed as an ERROR because there are some cases where nasty problems
can occur (if the TTLs vary from the NS records at the root servers and the
NS records point to your own domain, for example).


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:
ns1.dreamhost.com.
ns2.dreamhost.com.
ns3.dreamhost.com.


ERROR: Some of your nameservers listed at the parent nameservers
did not respond. The ones that did not respond are:

66.33.206.206



#2

It doesn’t really matter, but if if bugs you, write support with a list, and have them put it in my queue, and I’ll fix it for you.