Zimbra 5 install on CentOS 5 / MX Record

[MrBryce2000]

One more thing, the DNS in a nutshell assumed that BIND was running on the same server as Zimbra. Shouldn't I have it run on the server that's handling our Internet traffic instead? If so, then would the settings be the same?

[MrBryce2000]

Ok, I disabled BIND on the server that will run Zimbra, and set it up on the server that is handling the Internet traffic. Here is the configuration of the fairhavenchurch.org master zone.

$ttl 38400
fairhavenchurch.org.	IN	SOA	intranet.fairhavenchurch.org. root.localhost. (
			1208727739
			10800
			3600
			604800
			38400 )
@	IN	NS	intranet.fairhavenchurch.org.
@	      IN	A	192.168.1.153
mail.fairhavenchurch.org.	IN	A	192.168.1.153
@	IN	MX	10 mail
mail1       IN	      CNAME	mail
mail2       IN        CNAME     mail

The A record works, but not the MX record. I'm sure it's something silly that I've missed. Just a FYI, "intranet.fairhavenchurch.org" is the hostname for the server that is handling the Internet traffic.

[webman]

Have you tried this way round, how you had it before?

mail IN A     192.168.1.153
@    IN MX 10 mail.fairhavenchurch.org.

[Bill Brock]

If you plan on using mail1 and/or mail2 as pointing to your mail server, I believe the RFC's recommend not using cname's to point to a mail server. They recommenf using A eacords only.

[phoenix]

This would be the format you want.

Originally Posted by webman

Have you tried this way round, how you had it before?

mail IN A     192.168.1.153
@    IN MX 10 mail.fairhavenchurch.org.

You also have an incorrect hosts file (you're missing localhost IP), it should be this:

# Do not remove the following line, or various programs
# that require network functionality will fail.
192.168.1.153	mail.fairhavenchurch.org	mail
127.0.0.1 localhost.localdomain	localhost

[uxbod]

localhost entry is wrong

192.168.1.153	mail.fairhavenchurch.org	mail
127.0.0.1 localhost.localdomain	localhost	
::1	localhost6.localdomain6	localhost6

[MrBryce2000]

Thank you very much, everyone, for your help!! Because of you, progress is finally being made!

The server that is handling the Internet traffic is handling the DNS as well. Are the following OK?

dig mail.fairhavenchurch.org a

; <<>> DiG 9.3.3rc2 <<>> mail.fairhavenchurch.org a
;; global options:  printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 47716
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;mail.fairhavenchurch.org.	IN	A

;; ANSWER SECTION:
mail.fairhavenchurch.org. 38400	IN	A	192.168.1.153

;; AUTHORITY SECTION:
fairhavenchurch.org.	38400	IN	NS	intranet.fairhavenchurch.org.

;; Query time: 1 msec
;; SERVER: 192.168.1.155#53(192.168.1.155)
;; WHEN: Tue Apr 22 13:45:00 2008
;; MSG SIZE  rcvd: 81

dig mail.fairhavenchurch.org mx

; <<>> DiG 9.3.3rc2 <<>> mail.fairhavenchurch.org mx
;; global options:  printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 12150
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;mail.fairhavenchurch.org.	IN	MX

;; AUTHORITY SECTION:
fairhavenchurch.org.	38400	IN	SOA	intranet.fairhavenchurch.org. root.localhost. 1208727739 10800 3600 604800 38400

;; Query time: 1 msec
;; SERVER: 192.168.1.155#53(192.168.1.155)
;; WHEN: Tue Apr 22 13:44:29 2008
;; MSG SIZE  rcvd: 101

THANKS AGAIN!!

[uxbod]

Okay the second dig is not correct. If the domain you wish to receive email for is fairhavenchurch.org then test with

dig fairhavenchurch.org mx

the receiving server from what I read should be mail.fairhavenchurch.org. When checking the MX you have to specify the domain you are interested in, and not the actual server name. The first dig looks good so to do a final pass try the following

host `hostname` <- note backticks and not double quotes
dig fairhavenchurch.org mx
dig mail.fairhavenchurch.org a

if you are sending out to the Internet direct, and not using a upstream mail server ie. your ISP make sure other domains resolve aswell so try

dig yahoo.com mx

and you should see their MX records.

[MrBryce2000]

host 'mail.fairhavenchurch.org'

[root@mail ~]# host 'mail.fairhavenchurch.org'
mail.fairhavenchurch.org has address 192.168.1.153

dig fairhavenchurch.org mx

; <<>> DiG 9.3.3rc2 <<>> fairhavenchurch.org mx
;; global options:  printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 13712
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;fairhavenchurch.org.           IN      MX

;; ANSWER SECTION:
fairhavenchurch.org.    38400   IN      MX      10 mail.fairhavenchurch.org.fairhavenchurch.org.

;; AUTHORITY SECTION:
fairhavenchurch.org.    38400   IN      NS      intranet.fairhavenchurch.org.

;; Query time: 1 msec
;; SERVER: 192.168.1.155#53(192.168.1.155)
;; WHEN: Sat Apr 26 11:42:39 2008
;; MSG SIZE  rcvd: 101

dig mail.fairhavenchurch.org a

; <<>> DiG 9.3.3rc2 <<>> mail.fairhavenchurch.org a
;; global options:  printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 33816
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;mail.fairhavenchurch.org.      IN      A

;; ANSWER SECTION:
mail.fairhavenchurch.org. 38400 IN      A       192.168.1.153

;; AUTHORITY SECTION:
fairhavenchurch.org.    38400   IN      NS      intranet.fairhavenchurch.org.

;; Query time: 2 msec
;; SERVER: 192.168.1.155#53(192.168.1.155)
;; WHEN: Sat Apr 26 12:43:05 2008
;; MSG SIZE  rcvd: 81

[phoenix]

When doing any dig commands you should only use the domain name not the FQDN of your server, the correct check for the A record would be:

dig fairhavenchurch.org any

Also the test for the hostname must be in this format:

host `hostname`  <-- that's backticks not single quotes

you must enter the word 'hostname' not the FQDN of your mailserver and that will test if your your /etc/hosts file is correct.