Zimbra offers Open Source email server software and shared calendar for Linux and the Mac
Go Back   Zimbra :: Forums > Zimbra Collaboration Suite > Installation

Welcome to the Zimbra :: Forums!
Welcome, if you would like to post a comment please register. We also encourage you to explore all things Zimbra with our team and members of the community.

Reply
 
LinkBack Thread Tools Search this Thread Display Modes
  #1 (permalink)  
Old 09-04-2009, 12:27 PM
Senior Member
 
Posts: 70
Default Split dns working, but Zimbra can't resolve MX

It works fine in DiG, but I still get:

DNS ERROR resolving MX mail.mydomain.com

when I try to install Zimbra.

Really getting tired of trying to get this thing to work.

The ldap also fails to start, but my guess is that it is related to the DNS fail.
__________________
- Misty
Reply With Quote
  #2 (permalink)  
Old 09-04-2009, 12:38 PM
Zimbra Consultant & Moderator
 
Posts: 20,316
Default

The usual question, post the output of the following command run on the Zimbra server:

Code:
cat /etc/hosts
cat /etc/resolv.conf
dig yourdomain.com mx
dig yourdomain.com any
host `hostname`  <-- use that exact command with backticks not single quotes
Please update your forum profile with the output (do not post it in this thread) of the following:

Code:
zmcontrol -v
__________________
Regards


Bill
Reply With Quote
  #3 (permalink)  
Old 09-04-2009, 02:35 PM
Senior Member
 
Posts: 70
Default

Here's the info (moved from my DNS thread):


cat /etc/hosts

Code:
127.0.0.1	localhost.localdomain	localhost
192.168.5.5	mail.mydomain.com	mail
cat /etc/resolv.conf

Code:
search mydomain.com
nameserver 192.168.5.5
dig mydomain.com mx

Code:
;; QUESTION SECTION:
;mydomain.com.	IN	MX

;; ANSWER SECTION:
mydomain.com.	3600	IN	MX	10 mail.mydomain.com.

;; AUTHORITY SECTION:
mydomain.com.	3600	IN	NS	192.168.5.5.mydomain.com.

;; ADDITIONAL SECTION:
mail.mydomain.com. 3600	IN	A	192.168.5.5

;; Query time: 0 msec
;; SERVER: 192.168.5.5#53(192.168.5.5)
(etc.)
dig mydomain.com any

Code:
;; QUESTION SECTION:
;mydomain.com.	IN	ANY

;; ANSWER SECTION:
mydomain.com. 3600	IN	SOA	mydomain.com. mail.mydomain.com. 3339765489 86400 86400 24192 3600
mydomain.com. 3600	IN	NS	192.168.5.5.mydomain.com.
mydomain.com. 3600	IN	MX	10 mail.mydomain.com.

;; ADDITIONAL SECTION:
mail.mydomain.com. 3600	IN	A	192.168.5.5

;; Query time: 0 msec
;; SERVER: 192.168.5.5#53(192.168.5.5)
(etc.)
host `hostname`

Code:
Host mail not found: 3(NXDOMAIN)
Now if I type hostname, I get mail as a response, but for some reason the host `hostname` command can't find it. I have no idea what this indicates
__________________
- Misty
Reply With Quote
  #4 (permalink)  
Old 09-04-2009, 06:36 PM
Loyal Member
 
Posts: 82
Default

hi misty...

this is for Ubuntu.. but the DNS stuff is the same.. please follow steps carefully.. and do the testing before you install..
I am assuming from your records listed above you are using split dns..?
If not let me know..
silly question.. but your using your domain info in the right spots instead of mydomain.com right..?

just look over the DNS stuff at the beginning of this for Ubuntu

Ubuntu 8.04 LTS Server - Zimbra :: Wiki
Reply With Quote
  #5 (permalink)  
Old 09-04-2009, 08:37 PM
Intermediate Member
 
Posts: 18
Default

Isn't that message "DNS ERROR resolving MX mail.mydomain.com" means you are doing it correctly, but just need to change the domain name from "mail.mydomain.com" to "mydomain.com" ?
Reply With Quote
  #6 (permalink)  
Old 09-05-2009, 12:50 AM
Moderator
 
Posts: 7,928
Default

Please post your DNS zone file.
__________________
Reply With Quote
  #7 (permalink)  
Old 09-08-2009, 12:22 PM
Senior Member
 
Posts: 70
Default

As it turns out, it was a combination of the FQDN and the firewall rule that allowed the machine to talk to itself on the LDAP port (or didn't). It has been changed for a more specific rule.

The zone file is fine, it is now working with no changes.

What I don't get is why Zimbra needs to talk to itself on the local IP rather than the localhost loopback (127.0.0.1), atmail doesn't have to do this. And I am not impressed with having to change my traditional Unix-style machine names (asterix, obelix, getafix, cacofonix) to Microsoft-style descriptive names just to install an email server.
__________________
- Misty
Reply With Quote
  #8 (permalink)  
Old 09-08-2009, 12:38 PM
Zimbra Consultant & Moderator
 
Posts: 20,316
Default

Quote:
Originally Posted by Mistoffeles View Post
What I don't get is why Zimbra needs to talk to itself on the local IP rather than the localhost loopback (127.0.0.1), atmail doesn't have to do this.
It's a requirement of Postfix that it's able to resolve it's IP address via DNS.

Quote:
Originally Posted by Mistoffeles View Post
And I am not impressed with having to change my traditional Unix-style machine names (asterix, obelix, getafix, cacofonix) to Microsoft-style descriptive names just to install an email server.
The FQDN is a requirement for Linux servers in general, it's not a 'Microsoft Style' of anything. You can call your machines anything they like as long as they're part of a FQDN.
__________________
Regards


Bill
Reply With Quote
  #9 (permalink)  
Old 09-14-2009, 09:53 AM
Senior Member
 
Posts: 70
Default

I have several machines that do not have their host name set to the FQDN. They have to trouble sending mail (using sendmail) using the FQDN.

A lot of UNIX computers at universities do not send mail as "Garfield", "Odie", or whatever name they are given.

Heck I have even seen Exchange servers set up to send mail as something other than the hostname they are given on the local/internal network, although it takes some fiddling.
__________________
- Misty
Reply With Quote
Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes


Similar Threads

Why Join?

Registering let's you ask questions, makes it easier to search, displays any files attached to posts, and notifies you about replies.

blog.zimbra.com




 

SEO by vBSEO ©2011, Crawlability, Inc.