Need help setting up domain for mailserver.

[CalmingStorm]

Greetings, I'm currently running Ubuntu 10.4 LTS, I've installed Zimbra and DNSMASQ Successfully running a split DNS, I can send/receive emails through zimbra locally.

I had my domain registered at Dreamhost, I did my best to set the MX records - I could receive emails externally but not send, we recently migrated to GoDaddy, now we're back to local only.

Basically, the question I'm asking is this :

I'm very good with setting server-side equipment and software up, the server is setup entirely correct and ports are all forwarded, and if we access it via IP it pings to the outside world.

What do I need to do on my DOMAIN to make this fully work?

My server is zimbra.ciied.org, I of course send mail from ciied.org directly. But the actual mail server is configured as zimbra.ciied.org.

What records/dns settings do I need to put on my domain that tie back to my computer, as far as MX/A/DNS records go.

I'm lost at this point, server is done, configured - split dns in place. I just have no idea what to enter on GoDaddy (my handler for ciied.org) to complete the loop so that I can send and receive to the outside world.

[CalmingStorm]

Heres my configuration at Godaddy, I know this is the problematic part. I have the sub domain of zimbra.ciied.org directed to the IP of the server thats handling both mail and dns.

Any help at all would be greatly appreciated, I know you guys deal with a lot of questions and I can promise I've read through most every help page - I'm just stuck.


Nameservers: (Last update 1/25/2012)
NS15.DOMAINCONTROL.COM
NS16.DOMAINCONTROL.COM
ZIMBRA.CIIED.ORG
NS1.DREAMHOST.COM

DNS Manager:
A @ 64.202.189.170
A zimbra 71.162.114.14
CNAME e email.secureserver.net
CNAME email email.secureserver.net
CNAME ftp @
MX zimbra zimbra.ciied.org

[CalmingStorm]

All taken care of, thanks anyways guys!

[vijayv_us]

Originally Posted by CalmingStorm

All taken care of, thanks anyways guys!

can you post the solution here

[Crayz9000]

I'm guessing that the DNS changes had not propagated yet.

For what it's worth, it appears that the domains are backward now. Going to ciied.org pulls up the Zimbra webmail interface, while going to zimbra.ciied.org pulls up the "Hello, Cambridge Employee!" page.

Here's the OP's DNS:

$ dig @8.8.8.8 -t any ciied.org

; <<>> DiG 9.4.3-P3 <<>> @8.8.8.8 -t any ciied.org
; (1 server found)
;; global options:  printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 22273
;; flags: qr rd ra; QUERY: 1, ANSWER: 6, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;ciied.org.			IN	ANY

;; ANSWER SECTION:
ciied.org.		1800	IN	MX	10 zimbra.ciied.org.
ciied.org.		1800	IN	MX	5 zimbra.ciied.org.
ciied.org.		3600	IN	A	64.202.189.170

;; Query time: 111 msec
;; SERVER: 8.8.8.8#53(8.8.8.8)
;; WHEN: Mon Apr 23 11:15:03 2012
;; MSG SIZE  rcvd: 186

and

$ dig @8.8.8.8 -t any zimbra.ciied.org

; <<>> DiG 9.4.3-P3 <<>> @8.8.8.8 -t any zimbra.ciied.org
; (1 server found)
;; global options:  printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 55050
;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;zimbra.ciied.org.		IN	ANY

;; ANSWER SECTION:
zimbra.ciied.org.	1800	IN	AAAA	2002::47a2:720e
zimbra.ciied.org.	1800	IN	A	71.162.114.14

;; Query time: 2110 msec
;; SERVER: 8.8.8.8#53(8.8.8.8)
;; WHEN: Mon Apr 23 11:15:44 2012
;; MSG SIZE  rcvd: 78

For comparison, here's Google's DNS records (trimmed to omit the unnecessary fluff):

$ dig @8.8.8.8 -t any google.com
;; Truncated, retrying in TCP mode.

; <<>> DiG 9.4.3-P3 <<>> @8.8.8.8 -t any google.com
; (1 server found)
;; global options:  printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 42459
;; flags: qr rd ra; QUERY: 1, ANSWER: 33, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;google.com.			IN	ANY

;; ANSWER SECTION:
google.com.		299	IN	A	74.125.224.165
google.com.		599	IN	MX	10 aspmx.l.google.com.

;; Query time: 129 msec
;; SERVER: 8.8.8.8#53(8.8.8.8)
;; WHEN: Mon Apr 23 11:11:32 2012
;; MSG SIZE  rcvd: 700

and

$ dig @8.8.8.8 -t any aspmx.l.google.com

; <<>> DiG 9.4.3-P3 <<>> @8.8.8.8 -t any aspmx.l.google.com
; (1 server found)
;; global options:  printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 56066
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;aspmx.l.google.com.		IN	ANY

;; ANSWER SECTION:
aspmx.l.google.com.	293	IN	A	173.194.77.26

;; Query time: 51 msec
;; SERVER: 8.8.8.8#53(8.8.8.8)
;; WHEN: Mon Apr 23 11:14:22 2012
;; MSG SIZE  rcvd: 52

Aside from the IP addresses being switched around, which would obviously make mail not deliver properly, you only need one MX record if you have one MX server. The usual is a priority 10 MX record for one server; additional (fallback) servers can be set with larger priority values.