Re: [cobalt-users] RE: RAQ4i MX Records

[Jeff Lasman <jblists@xxxxxxxxxxxxx>]

Paul Andringa wrote:

> SECOND REQUEST: ANYBODY THERE THAT CAN HELP?

I'll try.

> I am having some problems when testing my DNS settings using
> http://www.dnsreport.com
> It seems to timeout waiting for the MX Records.
> I also get when looking for the MX record:
> 
> Searching for MX record for andringa.net at NS1.andringa.net.:  Reports that
> no MX records exist. [took 125 ms]
> Answer: No MX records exist for andringa.net. [Neg TTL=86400 seconds]
> 
> Details:
> NS1.andringa.net. (an authoritative nameserver for andringa.net.) says that
> there are no MX records for andringa.net.

That's true.  ns1.andringa.net and ns2.andringa.net both show no MX
records.

> The DNS is configured and has an MX Record in there, see example below.
> 
> andringa.net        --> 217.204.38.172
> mail.andringa.net   --> 217.204.38.172
> www.andringa.net    --> 217.204.38.172
> mail.andringa.net   --- mail is sent to the High priority mail server ---
> andringa.net

Have you clicked on "save changes"?

> This is the NSLOOKUP Result:
> 
> ls -d andringa.net
> [ns1.andringa.net]
> andringa.net.    SOA    ns1.andringa.net dns.andringa.net.  (20020 51619
> 3600 3600 04800 86400)
> andringa.net.    NS     ns1.andringa.net
> andringa.net.    NS     ns2.andringa.net
> andringa.net.    A      217.204.38.172
> ns2              A      217.204.38.173
> mail             A      217.204.38.172
> mail             MX     30   andringa.net
> www              A      217.204.38.172
> ns1              A      217.204.38.172
> andringa.net.    SOA    ns1.andringa.net dns.andringa.net. (20020 51619 3600
> 3600 604800 86400)

This is interesting, because when I do the same I also get an mx record.

> All is working fine, mail is coming and this is not the problem. The result
> is the same for all Virtual Domains.  It is just that it is not responding
> correctly.

This is NOT fine, since a direct nslookup (which uses the resolver) does
NOT find the MX record it's only working because mailservers are falling
back to use A records, which is NOT the best of ideas <frown>.

So resolvers aren't properly getting the information from bind, but the
zone transfer looks fine.

Very weird.

I'd try refreshing the bind rpm if I were you; Cobalt product (s)rpms
are available at ftp-eng.cobalt.com.

If that doesn't work, or if you're not willing to take the risk involved
in doing it yourself, then you're probably going to need someone to look
into your system.  You SHOULD fix this; it could cause you problems in
receiving email at some point.

Jeff
-- 
Jeff Lasman <jblists@xxxxxxxxxxxxx>
Linux and Cobalt/Sun/RaQ Consulting
nobaloney.net
P. O. Box 52672, Riverside, CA  92517
voice: (909) 778-9980  *  fax: (702) 548-9484