Results 1 to 5 of 5

Thread: Problem with MX record

  1. #1
    Join Date
    May 2006
    Posts
    196
    Rep Power
    9

    Default Problem with MX record

    Hi,

    we have a problem setting up Zimbra on our server due to some trouble with mx.

    when running install.sh, after installing the rpms and configuration we get:

    Code:
    DNS ERROR resolving MX for zimbra.systrade.de
    The server resolves in DNS and is configured as a MX in the DNS.
    Here is the output of dig mx systrade.de

    Code:
    ; <<>> DiG 9.2.4 <<>> mx systrade.de
    ;; global options:  printcmd
    ;; Got answer:
    ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 32425
    ;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 1, ADDITIONAL: 2
    
    ;; QUESTION SECTION:
    ;systrade.de.                   IN      MX
    
    ;; ANSWER SECTION:
    systrade.de.            172800  IN      MX      10 zimbra.systrade.de.
    
    ;; AUTHORITY SECTION:
    systrade.de.            172800  IN      NS      sys2001.systrade.de.
    
    ;; ADDITIONAL SECTION:
    zimbra.systrade.de.     172800  IN      A       10.1.20.61
    sys2001.systrade.de.    172800  IN      A       192.168.100.201
    
    ;; Query time: 88 msec
    ;; SERVER: 192.168.100.201#53(192.168.100.201)
    ;; WHEN: Sun Jun  4 10:41:52 2006
    ;; MSG SIZE  rcvd: 106
    /etc/hosts looks like this


    Any idea how to resolve this?

    Code:
    127.0.0.1       localhost.localdomain   localhost
    10.1.20.61      zimbra.systrade.de      zimbra
    I can go on in the install but later get a problem with the ldap connect and think the MX problem is the reason for that.
    So any idea what to do?

    Thanks

    Christian

  2. #2
    Join Date
    May 2006
    Posts
    19
    Rep Power
    9

    Lightbulb

    This is what I get when looking up the MX record for the domain:

    Code:
    systrade.de     mail exchanger = 10 systrade.de.
    systrade.de     mail exchanger = 20 mx01.schlund.de.
    
    Authoritative answers can be found from:
    systrade.de     nameserver = ns17.schlund.de.
    systrade.de     nameserver = ns18.schlund.de.
    ns17.schlund.de internet address = 195.20.224.120
    ns18.schlund.de internet address = 212.227.123.14
    ns17.schlund.de(195.20.224.120) is the primary DNS for the domain & needs the MX 10 record changed. Your local server (192.168.100.201) thinks it's the authoritive NS for the domain when infact ns17.schlund.de is. You need to modify the DNS "A" and MX" records on the authoritive DNS server. Also remove the 20 mx01.schlund.de record, or mail will also go to your hosting provider's server.

    After the changes, check your /etc/resolv.conf & get rid of the local DNS server entry, you'll find that when debugging DNS issues it's best to get the 'working' internet's view of your domain. Also a third opinion is good (especially when cached dns entries fool you):

    http://www.kloth.net/services/nslookup.php

  3. #3
    Join Date
    May 2006
    Posts
    196
    Rep Power
    9

    Default

    Thanks for your help, but what you found there is our external system at our providers site. This is currently totally separated from our internal mail system.

    The Zimbra server we are currently installing is an internal system.
    So the records you find have nothing to do with this system.


    Any other ideas?

  4. #4
    Join Date
    Apr 2006
    Posts
    27
    Rep Power
    9

    Default

    What is in your /etc/resolv.conf file?

  5. #5
    Join Date
    May 2006
    Posts
    196
    Rep Power
    9

    Default

    The /etc/resolv.conf is:

    Code:
    search systrade.de
    nameserver 192.168.100.201

    Another thing we tried:
    We separated the part of the zmsetup.pl script that checks for the MX record.
    And this is what the script gets returned:

    Code:
    MX: zimbra.systrade.de (10.1.20.61)
    Looks good to me.
    The only thing we changed was the line
    Code:
     my $ans = getDnsRecords($config{CREATEDOMAIN}, 'MX');
    Here we changed $config{CREATEDOMAIN} to 'systrade.de'

    The problem seems to be that $config{CREATEDOMAIN} contains "zimbra.systrade.de" at this point in the script and when we put this string into our test script it returns an error.

    Any idea what to do about this besides editing the script?

    Christian
    Last edited by chh; 06-13-2006 at 12:35 AM.

Similar Threads

  1. Issue: MX Record & Multi-domain
    By wcbenyip in forum Installation
    Replies: 5
    Last Post: 06-23-2009, 06:15 PM
  2. Replies: 11
    Last Post: 05-12-2009, 06:26 AM
  3. Zimbra, WM5.0, AS + problem with regional fonts
    By wojo2000 in forum Zimbra Mobile
    Replies: 7
    Last Post: 06-25-2007, 01:04 AM
  4. Is it started or not
    By kwelipatton in forum Installation
    Replies: 10
    Last Post: 03-28-2006, 10:11 PM

Posting Permissions

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