Quote:
Originally Posted by mmenaz  On default install, it complains that can't find MX for mail.example.com, and gives you the option to manually enter the domain. At this point I enter "example.com" and continue installation. I'm really puzzled about why it thinks that mail.example.com is the right default choice, so I join your dubts and ask:
a) the installer is foulty and shold be fixed?
b) I'm missing something, and there is a solid reason why I should have MX record for mail.example.com and example.com, and have these 2 domains (sure I have to create example.com in zimbra then) in a clean install? |
I'm sorry that you think this is an issue with the installer. I believe the installer is behaving properly, in this respect.
Your MX record shows "mail.jsr-domain.nl" as the proper server name. There's no need for a second MX record if your mail server and MX record are correctly matched for the domain. That is what your hostname should be and Zimbra expects that for name resolution too. To me, it appears that you shouldn't change the hostname during install.
DNS domains, MX, hostnames, mail domains and mail addresses are all related, but not the same thing. To someone new, it is easy to get confused, I guess.
www.domain.tld www = hostname
domain.tld = DNS domainname
mail.domain.tld mail = hostname
domain.tld = DNS domainname
domain.tld = mail domain
user@mail.domain.tld can be configured to resolve to
user@domain.tld in any email system that I've seen, but you can easily set an email domain alias in Zimbra to do this. How email routing works
http://www.faqs.org/docs/linux_netwo...l.routing.html may be helpful.
If you ever wondered why almost all web servers seem to be "www.domain.com"? "www" is just the hostname for the server. By convention, most companies use that, but they could just as easily named their web server (or server farm) "web", "peter", "jenny" or any other name that doesn't conflict with DNS name standards. The same usually applies to email servers. "mail.domain.com" just means that "mail" is the hostname for the server, by convention. ftp.domain.com, gopher.domain.com, ldap.domain.com, web.domain.com are further examples of mixing hostnames and DNS domainnames to get an external FQDN for a server.
I hope this helps and doesn't confuse anyone.