During i-MSCP setup (or on reconfiguration), the administrator will be asked for
- The <domain.tld> domain to use for the server, the control panel and the services (ftp, imap/pop, smtp)
- The <panel>.<domain.tld> subdomain to use for the control panel
- The <server>.<domain.tld> subdomain to use for the server hostname
Then, the installer will in order
- Configure the server hostname using the choosen <server>.<domain.tld> subdomain
- Create a DNS zone for <domain.tld> instead of a zone for <panel>.<domain.tld>
- Add a DNS record for the <panel>.<domain.tld> in the newly created zone
- Add a DNS record for the <server>.<domain.tld> in the newly created zone
- Add the DNS records for the services (smtp.<domain.tld>, pop.<domain.tld>, imap.<domain.tld>, ftp.<domain.tld>)
- All users will access mail and ftp services through the same domain names
- This will allows us to generate SSL certificates for all those names easily and avoid common name mismatch issues.
- This will allow also to mitigate reverse DNS issues
- Each customer will receive information for accessing the mail services.
To be discussed
Should we by default set the same NS in all zones? This is already possible with the https://github.com/i-MSCP/imsc…med/10_named_global_ns.pl listener file. The question is: should we do that by default.