[SOLVED] Unable to receive e-mail after domain move

[mrody]

Sorry in advace if this is a repeat post, but I tried searching and didn't find anything.

I recently changed the domain from mail.mydomain.com to mydomain.com, following this guide. I can send e=mail from the Zimbra accounts just fine, but whenever I try to send to the Zimbra account, it fails.

Here's the MX & ANY records

# dig odysseyzmail.net mx

; <<>> DiG 9.3.6-P1-RedHat-9.3.6-4.P1.el5_4.2 <<>> odysseyzmail.net mx
;; global options:  printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 10000
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;odysseyzmail.net.              IN      MX

;; ANSWER SECTION:
odysseyzmail.net.       43200   IN      MX      10 mail.odysseyzmail.net.

;; Query time: 132 msec
;; SERVER: 4.2.2.2#53(4.2.2.2)
;; WHEN: Mon Nov 22 12:13:09 2010
;; MSG SIZE  rcvd: 55

ANY

# dig odysseyzmail.net mx

; <<>> DiG 9.3.6-P1-RedHat-9.3.6-4.P1.el5_4.2 <<>> odysseyzmail.net mx
;; global options:  printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 10000
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;odysseyzmail.net.              IN      MX

;; ANSWER SECTION:
odysseyzmail.net.       43200   IN      MX      10 mail.odysseyzmail.net.

;; Query time: 132 msec
;; SERVER: 4.2.2.2#53(4.2.2.2)
;; WHEN: Mon Nov 22 12:13:09 2010
;; MSG SIZE  rcvd: 55

Thanks for any help- and again, sorry if this is a noob question, but I'm an Exchange admin =P

[phoenix]

So what you're saying is that you renamed the domain as per the details on the link you gave, is that correct? You've also posted the same dig information twice. In the Split DNS article got to the 'Verify...' section and post the output of all the commands from that section in this thread.

[mrody]

Yes, I renamed the domain as per the details. Sorry about the same info- not used to Linux, so learning as I go here.

# host $(hostname)
mail.odysseyzmail.net has address 72.249.116.181
# cat /etc/resolv.conf
search odysseyisp.net
nameserver 4.2.2.2
nameserver 8.8.8.8
# 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
72.249.116.181 mail.odysseyzmail.net

[phoenix]

I also wanted to see the missing dig output as well, anyway the hosts file is incorrect and the following is what you've posted above:

# Do not remove the following line, or various programs
# that require network functionality will fail.
127.0.0.1 localhost.localdomain localhost
72.249.116.181 mail.odysseyzmail.net

The last line need to look like this (the rest of the hosts file is OK):

72.249.116.181 mail.odysseyzmail.net mail

This is a RHEL (or CentOS) server isn't it? Do you have a firewall and/or SElinux enabled? Are all the correct ports open for the firewall?

In addition, those DNS servers you have listed in your resolv.conf do not show any A record for your server when I do a dig from here and they seem to be giving inconsistent responses. Perhaps you should consider changing them to another set of servers such as the following:

212.27.53.252
212.27.54.252

or http://DNSAdvantage.com servers:

156.154.70.1
156.154.71.1

or the EasyDNS resolvers:

http://dnsresolvers.com/

205.210.42.205
64.68.200.200

[mrody]

Whoops, forgot about the other DIG:

# dig odysseyzmail.net any

; <<>> DiG 9.3.6-P1-RedHat-9.3.6-4.P1.el5_4.2 <<>> odysseyzmail.net any
;; global options:  printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 32608
;; flags: qr rd ra; QUERY: 1, ANSWER: 4, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;odysseyzmail.net.              IN      ANY

;; ANSWER SECTION:
odysseyzmail.net.       43169   IN      MX      10 mail.odysseyzmail.net.
odysseyzmail.net.       42386   IN      NS      ns3.odysseyisp.net.
odysseyzmail.net.       42386   IN      NS      ns2.odysseyisp.net.
odysseyzmail.net.       42386   IN      NS      ns1.odysseyisp.net.

;; Query time: 112 msec
;; SERVER: 4.2.2.2#53(4.2.2.2)
;; WHEN: Mon Nov 22 12:13:41 2010
;; MSG SIZE  rcvd: 120

I fixed the hosts file, and switched the DNS over to dnsresolvers.com, any idea on how long it might take for the updates to propogate so I can test it?

And will I have these sort of problems again if I need to switch the domain name again? When I had it as mail.mydomain.com everything worked fine, it was just annoying to get people used to typing that in the email address fields.

[phoenix]

I fixed the hosts file, and switched the DNS over to dnsresolvers.com, any idea on how long it might take for the updates to propogate so I can test it?.

As you can see from that output, there's no A record being returned, that should be OK now you've changed the resolv.conf.. There's still a problem of connecting to your server, I can't telnet to port 25 of your server from here. Are the ports on your firewall open and do you have SElinux enabled on the server?

[mrody]

As you can see from that output, there's no A record being returned, that should be OK now you've changed the resolv.conf.. There's still a problem of connecting to your server, I can't telnet to port 25 of your server from here. Are the ports on your firewall open and do you have SElinux enabled on the server?

Ports are open (& I was able to telnet in on 25 & 443), and the software firewall is off, as is SElinux.

I'm at a total loss here, as receiving worked just fine before I changed the domain name from @mail.mydomain.com to @mydomain.com

[phoenix]

I'm at a total loss here, as receiving worked just fine before I changed the domain name from @mail.mydomain.com to @mydomain.com

First, you should confirm that the dig results return the correct information (it does as far as I can see). Second, assuming you've posted your correct domain name then I can't telnet to your server from here - it just times out. I'd suggest you go to one of these sites and check that the port is actually open. If it's not open then the culprit could be: your ISP blocking port 25; your firewall; your NAT router/hardware firewall(if you have one) to name but a few.

[mrody]

Ended up reenabling the firewall, rebooting, then disabling the firewall again, rebooting, and problems seem to be solved.

[phoenix]

Ended up reenabling the firewall, rebooting, then disabling the firewall again, rebooting, and problems seem to be solved.

Strange solution but inventive. Glad you've fixed it.