Results 1 to 7 of 7

Thread: DNS error resolving MX...

  1. #1
    Stergil is offline Senior Member
    Join Date
    May 2007
    Posts
    71
    Rep Power
    8

    Question DNS error resolving MX...

    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.
    Code:
    > 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.
    Code:
    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.

    Code:
    root@zimbra:~# cat /etc/hosts
    127.0.0.1       localhost
    192.168.0.10    zimbra.foostuff.com    zimbra
    Code:
    > 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?

  2. #2
    riegersteve is offline Senior Member
    Join Date
    Sep 2005
    Location
    Los Angeles
    Posts
    51
    Rep Power
    9

    Default

    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

  3. #3
    Bill Brock is offline Outstanding Member
    Join Date
    May 2007
    Location
    Oklahoma
    Posts
    703
    Rep Power
    9

    Default MX resolution

    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.

  4. #4
    shezzski is offline New Member
    Join Date
    Sep 2007
    Posts
    3
    Rep Power
    7

    Default

    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)

  5. #5
    shezzski is offline New Member
    Join Date
    Sep 2007
    Posts
    3
    Rep Power
    7

    Default

    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

  6. #6
    mmorse's Avatar
    mmorse is offline Moderator
    Join Date
    May 2006
    Location
    USA
    Posts
    6,242
    Rep Power
    21

    Default

    Quote Originally Posted by shezzski View Post
    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
    Last edited by mmorse; 09-28-2007 at 06:22 PM. Reason: quote

  7. #7
    farrukhndm is offline Special Member
    Join Date
    Aug 2008
    Location
    Pakistan
    Posts
    100
    Rep Power
    7

    Default Resolved

    i was also facing same problem in installation of z 7.0.1 .so by change FQDN name to domain name resolve my problem .

    Quote Originally Posted by shezzski View Post
    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 [/QUOTE]
    Last edited by phoenix; 03-29-2011 at 04:34 AM.

Thread Information

Users Browsing this Thread

There are currently 1 users browsing this thread. (0 members and 1 guests)

Similar Threads

  1. split dns isn't working for me....
    By lucidblue in forum Installation
    Replies: 5
    Last Post: 06-02-2007, 09:24 PM
  2. :( DNS Lookup issues
    By jhgutierrezg in forum Administrators
    Replies: 3
    Last Post: 05-30-2007, 08:00 AM
  3. ZCS ROCKS! Need some DNS help!
    By SiteDiscovery in forum Administrators
    Replies: 9
    Last Post: 12-30-2006, 10:50 PM
  4. DNS in a nutshell part two (For dummies)
    By daimer77 in forum Installation
    Replies: 4
    Last Post: 12-18-2006, 06:28 PM
  5. DNS Strategies and Best Practices, and a SLES10 Request
    By LMStone in forum Administrators
    Replies: 4
    Last Post: 10-14-2006, 07:51 AM

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •