[SOLVED] Mail out good. Mail in routing problem

[kjurkic]

Howdy

It may already be posted somewhere here, but if so, I have missed it.

I have setup a ZCS server, and created a new domain (catchmusic.ca), with mail server (mail.catchmusic.ca). This is a valid domain, and I can login into my server using http://mail.catchmusic.ca

I can send out from the account no problem, but when I try to send in to the account, I get a bounce back with the following:
Note: Forwarded message is attached.
-------------------------------------------------------
This is the mail system at host mail.example.com.

I'm sorry to have to inform you that your message could not
be delivered to one or more recipients. It's attached below.

For further assistance, please send mail to postmaster.

If you do so, please include this problem report. You can
delete your own text from the attached returned message.

The mail system

: Host or domain name not found. Name service error for
name=mail.example.com type=A: Host not found
Reporting-MTA: dns; mail.example.com
X-Postfix-Queue-ID: 0925B1722031
X-Postfix-Sender: rfc822; kjurkic@yahoo.ca
Arrival-Date: Tue, 1 Dec 2009 13:06:07 +0000 (UTC)

Final-Recipient: rfc822; kendrick@catchmusic.ca
Original-Recipient: rfc822;kendrick@catchmusic.ca
Action: failed
Status: 5.4.4
Diagnostic-Code: X-Postfix; Host or domain name not found. Name service error
for name=mail.example.com type=A: Host not found
--------------------------------------------------------

I tried to change the server default in ZCS (mail.example.com) but the admin panel won't let me change or add a server....I know its likely simple, and that I will be embarrassed by the solution

thanks in advance
Ken

[Krishopper]

Is the server actually named "mail.example.com" in your Zimbra setup?

This sounds like a new install. If it is named as "mail.example.com", I would start over and re-install Zimbra and use the correct server names, just to clean that up and get it out of the way.

[phoenix]

Originally Posted by kjurkic

: Host or domain name not found. Name service error for
name=mail.example.com type=A: Host not found
Reporting-MTA: dns; mail.example.com
X-Postfix-Queue-ID: 0925B1722031
X-Postfix-Sender: rfc822; kjurkic@yahoo.ca
Arrival-Date: Tue, 1 Dec 2009 13:06:07 +0000 (UTC)

Have you set-up a Split DNS if your server is behind a NAT router?

Please run the following commands on your Zimbra server and post the results:

cat /etc/hosts
dig yourdomain.com any
dig yourdomain.com mx
host `hostname`  <-- uset that exact command with backticks not single quotes

[kjurkic]

Originally Posted by phoenix

Have you set-up a Split DNS if your server is behind a NAT router?

Please run the following commands on your Zimbra server and post the results:

cat /etc/hosts
dig yourdomain.com any
dig yourdomain.com mx
host `hostname`  <-- uset that exact command with backticks not single quotes

Hi Bill, Thanks for passing this on.

Please bear with me, as EMail is only 1 of 20 services I have to support as a 1-man dept here. I am comfortable with linux, not scared of CLI, and just barely bright enough to follow directions; definitely not a *nix guru by any stretch.

I first set this server up as an off-line tinkertoy, with everything set at default values. Once I knew it was up, I started adding a couple of domains, and finally the last one (catchmusic.ca - an idle domain I own) to test send/receive, so somewhere I must have fragged the server name, or virtual domain setting..

Seeing the printout of my hosts file makes me hope that a simple edit might be enough for cure this?

Below are the results of the commands:

root@zimbra:~# cat /etc/hosts
127.0.0.1 localhost mail.example.com
127.0.1.1 zimbra

#Required for IPv6 capable hosts
::1 ip6-localhost ip6-loopback
fe00::0 ip6-localnet
ff00::0 ip6-mcastprefix
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters
ff02::3 ip6-allhosts
root@zimbra:~# dig catchmusic.ca any

; <<>> DiG 9.4.2-P2 <<>> catchmusic.ca any
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 39060
;; flags: qr rd ra; QUERY: 1, ANSWER: 8, AUTHORITY: 6, ADDITIONAL: 7

;; QUESTION SECTION:
;catchmusic.ca. IN ANY

;; ANSWER SECTION:
catchmusic.ca. 10800 IN MX 5 mail.catchmusic.ca.
catchmusic.ca. 10800 IN SOA ns0.easydns.com. admin.easydns.com. 1259718819 21600 720
0 1209600 10800
catchmusic.ca. 10800 IN NS ns1.easydns.com.
catchmusic.ca. 10800 IN NS ns6.easydns.net.
catchmusic.ca. 10800 IN NS remote2.easydns.com.
catchmusic.ca. 10800 IN NS ns3.easydns.org.
catchmusic.ca. 10800 IN NS ns2.easydns.com.
catchmusic.ca. 10800 IN NS remote1.easydns.com.

;; AUTHORITY SECTION:
catchmusic.ca. 10800 IN NS remote1.easydns.com.
catchmusic.ca. 10800 IN NS ns1.easydns.com.
catchmusic.ca. 10800 IN NS ns6.easydns.net.
catchmusic.ca. 10800 IN NS remote2.easydns.com.
catchmusic.ca. 10800 IN NS ns3.easydns.org.
catchmusic.ca. 10800 IN NS ns2.easydns.com.

;; ADDITIONAL SECTION:
mail.catchmusic.ca. 10800 IN A 142.25.56.5
remote1.easydns.com. 2629 IN A 209.200.131.4
ns1.easydns.com. 136662 IN A 66.225.199.10
ns6.easydns.net. 112185 IN A 205.234.220.146
remote2.easydns.com. 2724 IN A 209.200.141.4
ns3.easydns.org. 52 IN A 209.200.177.4
ns2.easydns.com. 2629 IN A 72.52.2.1

;; Query time: 100 msec
;; SERVER: 10.0.0.1#53(10.0.0.1)
;; WHEN: Wed Dec 2 04:21:54 2009
;; MSG SIZE rcvd: 443

root@zimbra:~# dig catchmusic.ca mx

; <<>> DiG 9.4.2-P2 <<>> catchmusic.ca mx
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 28752
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 6, ADDITIONAL: 7

;; QUESTION SECTION:
;catchmusic.ca. IN MX

;; ANSWER SECTION:
catchmusic.ca. 10795 IN MX 5 mail.catchmusic.ca.

;; AUTHORITY SECTION:
catchmusic.ca. 10795 IN NS ns2.easydns.com.
catchmusic.ca. 10795 IN NS remote1.easydns.com.
catchmusic.ca. 10795 IN NS ns1.easydns.com.
catchmusic.ca. 10795 IN NS ns6.easydns.net.
catchmusic.ca. 10795 IN NS remote2.easydns.com.
catchmusic.ca. 10795 IN NS ns3.easydns.org.

;; ADDITIONAL SECTION:
mail.catchmusic.ca. 10795 IN A 142.25.56.5
remote1.easydns.com. 2624 IN A 209.200.131.4
ns1.easydns.com. 136657 IN A 66.225.199.10
ns6.easydns.net. 112180 IN A 205.234.220.146
remote2.easydns.com. 2719 IN A 209.200.141.4
ns3.easydns.org. 47 IN A 209.200.177.4
ns2.easydns.com. 2624 IN A 72.52.2.1

;; Query time: 22 msec
;; SERVER: 10.0.0.1#53(10.0.0.1)
;; WHEN: Wed Dec 2 04:21:58 2009
;; MSG SIZE rcvd: 313

root@zimbra:~# host `hostname`
zimbra.bms.bc.ca does not exist (Authoritative answer)
root@zimbra:~#

[phoenix]

Your hosts file should contain the following:

127.0.0.1 localhost mail.example.com
10.0.0.1 mail.catchmusic.ca mail  <-- that shouild point to your Zimbra LAN IP

You didn't post your resolv.conf but it should only have one entry and that should be for your DNS server at "10.0.0.1".

You also need to modify your DNS entries to point the A record at your LAN IP instead of your Public IP and that should suffice, make those changes and see how you get on. If there's any problem then run all of the commands again to verify your DNS settings, post them here if you wish.

[kjurkic]

Apologies to anyone who sees multiple posts of the above reply...I tried a few times to post, and may have crossposted to the wrong subject.

Sorry for any problems this may have caused.
regards
Ken

[phoenix]

Originally Posted by phoenix

Your hosts file should contain the following:

127.0.0.1 localhost mail.example.com
10.0.0.1 mail.catchmusic.ca mail  <-- that shouild point to your Zimbra LAN IP

You didn't post your resolv.conf but it should only have one entry and that should be for your DNS server at "10.0.0.1".

Oops, I see I didn't ask for it. I should have included this command:

cat /etc/resolv.conf

[kjurkic]

Hi Bill & thanks for the feedback

My Zimbra server is living on the public side, but I guess since the initial build was on a private lan, that may have borked it.

So what should my IP/Name settings be for a fully public facing install?

Or should I play it paranoid, and return the box to the private LAN and do port forwarding through my F/W?

Thanks in advance

regards
Ken

thanks in advance
Ken

[phoenix]

Originally Posted by kjurkic

Or should I play it paranoid, and return the box to the private LAN and do port forwarding through my F/W?

If there's no reason to have it on a public IP then I'd leave it behind your NAT router and forward the correct ports. If you do that then make the changes I've suggested.

[kjurkic]

Well, staff need access from around the world (lotta travellers here) and I am not sure how to re-bake my firewall/router to accept the traffic to my DNS correct public IP....

I guess if this stuff was easy, they wouldn't need me :P