MX Mail Server Greeting And Parent Status Fail DNS Report

Based upon a check of two known-good domains in my collection, both of which work and one of which uses Google Apps for e-mail, I believe dnscolos.com is broken. Ignore it.

Can you receive mail? Can other people receive mail from you? If so, odds are good your mail is working fine.

Yes, everything seems fine re sending receiving mail. I tested some domains here as well http://dnssy.com and again everything gets a pass along with some helpful pointers like:

"You have 5 nameservers. Too many nameservers cause larger packets, requiring more bandwidth. Although not necessary, you should consider reducing to 3 or 4 nameservers."

or

"Your SOA minimum TTL value is 3 mins 1 secs. This is interpreted by servers as the default TTL. It can be overridden on individual DNS entries. This seems low. Unless you are expecting frequent DNS changes or must react quickly to DNS changes you should consider increasing this value. Anything between 1 hour and 4 hours is OK with me."

@hoopycat:

Based upon a check of two known-good domains in my collection, both of which work and one of which uses Google Apps for e-mail, I believe dnscolos.com is broken. Ignore it.

Can you receive mail? Can other people receive mail from you? If so, odds are good your mail is working fine.

I'd probably trust that one about as far as I could throw it. Here's some gems from one of my domains:

> Your nameservers are all on the same class C IP namespace. This is an indication (but not proof) that they may be co-located, which could be a risk should the internet connection to that location fail.

(Even using the classic definition of "Class C" – a prefix length which we call /24 these days -- the nameservers are definitely not all in the same /24. Or the same /8. Or the same state. Or the same continent…)

> Your domain does not have a WWW record. This means that people will not be able to find your web site at http://www.hoopycat.com. Skipping further WWW tests.

(News to me!)

> Some of your MX servers do not have A records. I found problems with the following: mail.hoopycat.com

(I'm not sure the problems are with mail.hoopycat.com.)

Generally speaking, automated tools for checking DNS tend to suck. There's just too many stylistic differences, configuration choices, and different ways to do the same thing. Although I'm reasonably sure that this particular test was thrown for a loop by one of my nameservers being IPv6-only, the best bet is to have a greybeard look at your zonefile and see what they think.