DNS error resolving MX...

[Stergil]

I've seen quite a few posts about the MX error. In each case I've seen it seemed like folks didn't have the proper A/MX records in their internal DNS configured.

I'm far from an expert in DNS or Linux, but I think I have things setup properly.

nslookup with 'set q=mx' and fed 'foostuff.com' returns the following.

> foostuff.com
Server:         192.168.0.254
Address:        192.168.0.254#53

foostuff.com   mail exchanger = 10 zimbra.foostuff.com.

However, I still get the following error when running the install.sh script.

DNS ERROR resolving MX for zimbra.foostuff.com
It is suggested that the domain name have an MX record configured in DNS
Change domain name? [Yes]

If I continue the installation the services start properly. I'm not sure if it's a false-positive. I've not tried to configure things much yet thinking that I should resolve the installation error before getting too deep into configuration.

root@zimbra:~# cat /etc/hosts
127.0.0.1       localhost
192.168.0.10    zimbra.foostuff.com    zimbra

> zimbra.foostuff.com
Server:         192.168.0.254
Address:        192.168.0.254#53

Name:   zimbra.foostuff.com
Address: 192.168.0.10

Oh yea, Latest version of OpenSource Zimbra on Ubuntu 6.06.1-server.

Any thoughts?

[riegersteve]

on localhost do
ping zimbra.foostuff.com
if it comes back with your ip address then install. mail will work internally.
if you want mail to work externally you will have to setup NAT and DNS

[Bill Brock]

You are trying to resolve the MX for zimbra.foostuff.com instead of foostuff.com.

zimbra.foostuff.com is the FQDN of the mail server and foostuff.com is the domain. MX records are setup and resolved for domains.

The Zimbra install tries to set the domain to the FQDN of the server instead of the domain itself. During the install you must change the domain name that Zimbra wants to use to the domain name and not the FQDN of the host.

[shezzski]

I am having the same problem, I have Bind set up, but Zimbra somehow resolves the DNS records to the mail.example.com domain and not the example.com domain as I would like. When I change the domain to example.com I cannot even resolve the MX record.

I did remove the A record for the server so that I could get that error otherwise zimbra rolls on through and sets my domain as mail.example.com (something I dont want)

[shezzski]

Fixed this problem, I actually had MX record set up wrong (im using WEBMIN) and I had the name of the webserver set to mail.example.com. and mail server set to its IP address. I changed the name to example.com. and the mail server field set to mail.

I did still get the MX error as Bill Brock described, but now when I change to domain to example.com it resolved.

Thanks Bill for the post, and thanks for google finding it for me

Looking forward to playing more with ZIMBRA

[mmorse]

Originally Posted by shezzski

I did remove the A record for the server so that I could get that error otherwise zimbra rolls on through and sets my domain as mail.example.com (something I dont want)

btw-even if your 1st domain during setup is 'mail.domain.com' you can then add a 2nd 'domain.com' later -real easy CLI or from the admin console gui