all messages being deferred after server rename

[brettcave]

I have a problem with all emails (inbound and outbound) being deferred.

I initially had some extra hostnames in my /etc/hosts file:
1.2.3.4 somename.company.com somename demo.company.com demo mail.company.com company.com

company.com was initially used for install of zcs-5.0.4 rhel4. ldap server details (as per localconfig) referenced this. The original server `hostname` was demo.company.com, but changed a few months ago to somename.company.com. There were no issues with the server hostname change, as zimbra's naming stayed the same. I need to change the zimbra server name, so used the wiki as guidelines.

Error from /var/log/zimbra.log is:
status=deferred (Host or domain name not found. Name service error for name=somename.company.com type=A: Host not found, try again)

Configuration:
/etc/hosts:
127.0.0.1 localhost.localdomain
1.2.3.4 somename.company.com somename

/etc/resolv.conf (valid nameservers from service provider):
nameserver x.y.z.w
nameserver a.b.c.d

dig company.com mx:
company.com. 300 IN MX 10 somename.jemstep.com.
somename.company.com. 14400 IN A 1.2.3.4

dig company.com any:
company.com. 10618 IN A 7.8.9.10
## nameserver info - all on servers in different networks, working correctly ##

hostname:
somename.company.com

host `hostname`:
somename.company.com has address 1.2.3.4


seems resolution and dns is configured correctly, but all messages still getting deferred.

1 thing that might be related is that i remember working with zmlocalconf to get mailman integrated with zimbra:
postfix_mydestination = localhost company.com somename.company.com

also, zmlocalconfig shows ldap_host as company.com instead of somename.company.com. after changing this to somename.company.com, i get errors in zimbra.log:
postfix/trivial-rewrite: error: unable tio set STARTTLS: -1: can't contact ldap server

have just updated ldap_url from ldap://somename.company.com to ldap://somename.company.com:389 to see if that helps.

[uxbod]

Check /var/log/zimbra.log to see while Postfix is not delivering them.

[captainmish]

Looks like its just DNS resolution thats broken (Host not found, try again), make sure you can resolve these hosts with dig/host/ping on the system before changing any zimbra stuff (check /etc/resolv.conf, add your dns server to that: nameserver your.dns.server.ip)

[brettcave]

my resolution works fine. whether i use host / ping / dig, manually specifying nameservers or letting pam take care of name resolution order (i.e from hosts file first), it always seems to resolve.

i just discovered selinux was enforcing, rebooting now with it disabled.