[QUOTE=Easgs;16451]I have a doub about configuring suse for zimbra
in dns the mx record for the server is mail.sienic.site with A record mail 192.168.1.11, but in the hosts file suse setup the real hostname of the server in the hosts file as follow:
192.168.1.11 server03.sienic.site server03
(server03 is the real name of the server in /etc/hostname)
192.168.1.11 mail.sienic.site mail
in this scenario what would be the correct form of the hosts file?[/QUOTE]
You left out two important parts of the scenario:
- Does your server use it’s DNS server for name resolution, too?
Resolving “mail.sienic.site” to an IP address can be done via DNS (you’ve got the appropriate record set up), so there’s no need to add that info to /etc/hosts as well - if you server uses it’s DNS server for name resolution (which it should).
- Do you experience problems due to the host name variation?
It is not uncommon to name a server (“hostname”) differently from it’s DNS name, and many servers even have multiple DNS names. So unless Simbra requires the host name to be identical to the DNS name, you shouldn’t be in trouble. Sometimes default values for some configuration items are derived from the host name, but as you are aware of the potential difference, it should be easy for you to spot such configuration items and change them accordingly.
[QUOTE=Easgs;16451]the other thing is tha zimbra requires the first line to be
127.0.0.1 localhost.localdomain localhost
but suse default is
is ok to change to meet zimbra requirements or it will break things?[/QUOTE]
I see no problem in adding this additional name in /etc/hosts. BTW, if you have more servers/hosts requiring such additions, you might look into adding these (common) name resolutions to you DNS.