I have an Ubuntu LAMP configuration. It's primary function is to host multiple Drupal websites (Drupal is configured so all sites share the same code base, modules, and themes but have separate databases). For each domain, a Google Apps account is set up and I either point the Google partner's registrar to the Linode Name Servers and add the MX and TXT records to my server using the Linode DNS manager, or I edit the A record on the registrar's DNS manager to my IP on my Linode. Both methods seem to work fine. But both also display the following issue.
Take, for example if I run a DNS Report on "http://siteTwo.com" using http://thednsreport.com there are no 'fails'. However, if I run a DNS Report using http://www.dnscolos.com/ I get the following 'fails':

Parent: Failed - Parent nameservers siteTwo.com > Your NS records at the parent server f.gtld-servers.net are: (blank)
Parent: Failed - Nameservers for domain in DNs siteTwo.com > Your NS records at your nameservers are: (blank)

MX: Failed - Mailserver greeting > The server should have an A record which points to the mailserver for the hostname which is presented in the greeting
ASPMX.L.GOOGLE.COM
220 mx.google.com ESMTP k1si7869646wbc.80
ALT1.ASPMX.L.GOOGLE.COM
220 mx.google.com ESMTP l6si1249023fam.56
ALT2.ASPMX.L.GOOGLE.COM
220 mx.google.com ESMTP u4si7257841bkz.55
ASPMX2.GOOGLEMAIL.COM
220 mx.google.com ESMTP u13si7264977bkz.36
ASPMX3.GOOGLEMAIL.COM
220 mx.google.com ESMTP 40si6538980wae.148
ASPMX4.GOOGLEMAIL.COM
220 mx.google.com ESMTP e7si7867029wbb.87
ASPMX5.GOOGLEMAIL.COM
220 mx.google.com ESMTP w6si7849201ybe.130

Does anyone know if these issues can be resolved (or if they need to be) when I am using Google Apps as the mail server?
Thanks

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."

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



(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...)



(News to me!)



(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.