SMTP host/MX problems

[pswartz]

Hi All,
Just when everything starting working... I had issues with trying to move my domain registrar (different soapbox, long story), anyway since the transfer didn't happen I am back with my original registrar and their DNS controls.
Now while I am in the Zimbra Admin Console, testing the MX record fails with this message:

Domain is configured to use SMTP host: mail.nchea.net. None of the MX records match this name.
Found the following MX records:
0 mail.nchea.net.

So to start troubleshooting:
zimbra@mail:~> host `hostname`
mail.nchea.net has address 98.175.60.230
mail.nchea.net mail is handled by 0 mail.nchea.net.
zimbra@mail:~>

and

zimbra@mail:~> dig mail.nchea.net

; <<>> DiG 9.3.4 <<>> mail.nchea.net
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 18399
;; flags: qr aa rd; QUERY: 1, ANSWER: 1, AUTHORITY: 4, ADDITIONAL: 4

;; QUESTION SECTION:
;mail.nchea.net. IN A

;; ANSWER SECTION:
mail.nchea.net. 3600 IN A 98.175.60.230

;; AUTHORITY SECTION:
nchea.net. 86400 IN NS ns1.nameresolve.com.
nchea.net. 86400 IN NS ns2.nameresolve.com.
nchea.net. 86400 IN NS ns3.nameresolve.com.
nchea.net. 86400 IN NS ns4.nameresolve.com.

;; ADDITIONAL SECTION:
ns1.nameresolve.com. 86400 IN A 64.94.117.196
ns2.nameresolve.com. 86400 IN A 63.251.83.82
ns3.nameresolve.com. 86400 IN A 66.150.161.132
ns4.nameresolve.com. 86400 IN A 64.94.31.110

;; Query time: 74 msec
;; SERVER: 64.94.117.196#53(64.94.117.196)
;; WHEN: Tue Jan 13 10:42:36 2009
;; MSG SIZE rcvd: 199

zimbra@mail:~>

It appears from the hostname and dig cmds, that everything "should" be okay, right?
Not sure what to change/fix.
I can receive now, but sending from the Webmail interface (only interface I have used) doesn't work.
I'm not sure what I should have in the "Web mail MTA Hostname" block --
"localhost" or "mail.nchea.net" -- I am using the later.

I understand there are several thing here,and I apologize but any help would be greatly appreciated.

I am running:
Release 5.0.11_GA_2695.SuSEES10_20081117054639 SuSEES10 FOSS edition

Thank you,
Patrick

[uxbod]

If you ZCS server is behind a firewall on a private LAN then you will need to set up Wiki :: Split DNS architecture.

[pswartz]

My server is behind a firewall but I have private a IP address. The correct ports are open through the firewall. Tried to make this install as simple as possible.

[uxbod]

You need to read through the Wiki entry. Once that is setup then please be so kind as to post

cat /etc/hosts
cat /etc/resolv.conf
dig yourdomain mx
dig yourdomain any
host `hostname` <- note backticks and not single quotes

[pswartz]

My apologizies.. I have a PUBLIC address...

dig nchea.net mx

; <<>> DiG 9.3.4 <<>> nchea.net mx
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 19574
;; flags: qr aa rd; QUERY: 1, ANSWER: 1, AUTHORITY: 4, ADDITIONAL: 5
;; QUESTION SECTION:
;nchea.net. IN MX
;; ANSWER SECTION:
nchea.net. 3600 IN MX 5 mail.nchea.net.
;; AUTHORITY SECTION:
nchea.net. 86400 IN NS ns1.nameresolve.com.
nchea.net. 86400 IN NS ns2.nameresolve.com.
nchea.net. 86400 IN NS ns3.nameresolve.com.
nchea.net. 86400 IN NS ns4.nameresolve.com.
;; ADDITIONAL SECTION:
mail.nchea.net. 3600 IN A 98.175.60.230
ns1.nameresolve.com. 86400 IN A 64.94.117.196
ns2.nameresolve.com. 86400 IN A 63.251.83.82
ns3.nameresolve.com. 86400 IN A 66.150.161.132
ns4.nameresolve.com. 86400 IN A 64.94.31.110

;; Query time: 73 msec
;; SERVER: 64.94.117.196#53(64.94.117.196)
;; WHEN: Tue Jan 13 14:24:00 2009
;; MSG SIZE rcvd: 215

AND

; <<>> DiG 9.3.4 <<>> nchea.net any
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 6408
;; flags: qr aa rd; QUERY: 1, ANSWER: 7, AUTHORITY: 0, ADDITIONAL: 5
;; QUESTION SECTION:
;nchea.net. IN ANY
;; ANSWER SECTION:
nchea.net. 86400 IN SOA ns1.nameresolve.com. hostmaster.nchea.net. 2009011308 16384 2048 1048576 2560
nchea.net. 86400 IN NS ns1.nameresolve.com.
nchea.net. 86400 IN NS ns2.nameresolve.com.
nchea.net. 86400 IN NS ns3.nameresolve.com.
nchea.net. 86400 IN NS ns4.nameresolve.com.
nchea.net. 3600 IN MX 5 mail.nchea.net.
nchea.net. 3600 IN A 98.175.60.230
;; ADDITIONAL SECTION:
ns1.nameresolve.com. 86400 IN A 64.94.117.196
ns2.nameresolve.com. 86400 IN A 63.251.83.82
ns3.nameresolve.com. 86400 IN A 66.150.161.132
ns4.nameresolve.com. 86400 IN A 64.94.31.110
mail.nchea.net. 3600 IN A 98.175.60.230

host `hostname`
mail.nchea.net has address 98.175.60.230
mail.nchea.net mail is handled by 0 mail.nchea.net.

cat /etc/resolv.conf
nameserver 64.94.117.196
nameserver 98.175.60.227
nameserver 68.13.16.30
search swartzserves.com nchea.net

AND from /etc/hosts
98.175.60.230 mail.nchea.net mail

Also, for mail.nchea.net --- dig mx
;; ANSWER SECTION:
mail.nchea.net. 3600 IN MX 0 mail.nchea.net.

And -- dig any
;; ANSWER SECTION:
mail.nchea.net. 3600 IN MX 0 mail.nchea.net.
mail.nchea.net. 3600 IN A 98.175.60.230

[bofla]

I'm not sure I get how does this validates things, I'm getting same issue

Domain is configured to use SMTP host: mail.vm.local. None of the MX records match this name.
Found the following MX records:
0 mail.vm.local.

What it's trying to do here ?

[root@moo ~]# cat /etc/hosts
# Do not remove the following line, or various programs
# that require network functionality will fail.
127.0.0.1               localhost.localdomain localhost
::1             localhost6.localdomain6 localhost6
192.168.100.128 moo.vm.local    vm.local
[root@moo ~]# cat /etc/resolv.conf
; generated by /sbin/dhclient-script
search vm.local
nameserver 192.168.100.128
nameserver 192.168.100.2
[root@moo ~]# dig vm.local mx +short
0 mail.vm.local.
[root@moo ~]# dig vm.local any +short
vm.local. root.vm.local. 4 10800 900 604800 86400
ns.vm.local.
192.168.100.128
0 mail.vm.local.
[root@moo ~]# host `hostname`
moo.vm.local has address 192.168.100.128
[root@moo ~]#

This server is a VM test for Zimbra.

[phoenix]

I'm not sure I get how does this validates things, I'm getting same issue

It 'validates things' because it shows that you have no valid DNS A & MX records nor is you hosts file correct. Check the Quick Start Installation Guide for details or the hosts file, read the wiki article on Split DNS or search the forums for numerous post on what you need to do to fix it.

[bofla]

The fact that I replied to an existing post means I already looked at possible situations. If you want to help next time don't just bluntly point to docs.

Zimbra doesn't accept 0 as a valid priority (which it is, rfc974) which you could have pointed out in a much more helpful way. My entries were valid and this was the only culprit.

[phoenix]

The fact that I replied to an existing post means I already looked at possible situations. If you want to help next time don't just bluntly point to docs.

It doesn't show anything of the kind and I don't happen to be a mind reader. I don't happen to be a mind reader and perhaps next time you post you'll tell us what you've actually tried to fix the problem.

Zimbra doesn't accept 0 as a valid priority (which it is, rfc974) which you could have pointed out in a much more helpful way. My entries were valid and this was the only culprit.

Whether your priority is set to 0 in the MX records makes no difference to Zimbra, all that matters is what the response is to an MX lookup.

BTW, your hosts file is still incorrect. It would appear that you haven't bothered to read the documents that I pointed you to, have a look what the format of this statement should be:

192.168.100.128 moo.vm.local    vm.local

You'd also have found that if you'd searched the forums as it's one of the most common problems encountered here.

[bofla]

Sorry you can't read minds then

Change your MX to 0 and try on a clean setup and then change it to 10, you'll see what I mean.