I made a mistake on the version in my post. This problem is on SLES10. I have too many instances to list them all in the profile. I do need to update the Zimbra versions in my profile as the Zimbra instances are now at 5.0.3 or 4 or 5.
Apparently I sometimes have trouble following directions. Here is the host results hopefully exactly as requested.
Code:
msps2@msp:~> host `hostname`
msp.domain.local has address 192.168.2.3
msp.domain.local mail is handled by 10 msp.domain.local.
Code:
msps2@msp:~> cat /etc/hosts
#
# hosts This file describes a number of hostname-to-address
# mappings for the TCP/IP subsystem. It is mostly
# used at boot time, when no name servers are running.
# On small systems, this file can be used instead of a
# "named" name server.
# Syntax:
#
# IP-Address Full-Qualified-Hostname Short-Hostname
#
127.0.0.1 localhost
# special IPv6 addresses
::1 localhost ipv6-localhost ipv6-loopback
fe00::0 ipv6-localnet
ff00::0 ipv6-mcastprefix
ff02::1 ipv6-allnodes
ff02::2 ipv6-allrouters
ff02::3 ipv6-allhosts
192.168.2.3 msp.domain.local msp
192.168.2.4 mail.domain.local mail
Note the mail.domain.local is not used. Zimbra is provisioned as msp.domain.local.
I do vaguely recall from a couple of years ago that there was some Bind or Samba bug in SLES9.1 regarding using a domain name with a .local suffix. This is the only one of the Zimbra instances I have running on a .local TLD.
Thanks