Hello Hestia community,
I noticed the following in a couple of Hestia installations, and I would like your thoughts on this. But first some info:
HestiaCP Version: 1.0.6, release OS & Version: Ubuntu 18.04.3 LTS Installed Software: apache+nginx, multi-php, bind9, exim4, MariaDB
Steps to replicate the issue
- Create a user via Web-UI and login that user (through admin)
- Click Web > Add Web Domain
- Type in the domain name (e.g. xxx.yyy) > Either Select or not select the check box to create DNS zone (it doesn’t matter, since the outcome is the same in both cases) > Save
- Click Back > Click on domain
The actual Issue
By default 2 Aliases were created:
I can understand the first one, but what about the second alias? I guess it is created as another way to access the site, instead of the domain name (when for example we want to be able to access a new site that is being developed without using the domain name).
If that was the case, a DNS record should have been created in order to resolve xxx-yyy.[Server-FQDN]. But this is not bullet-proof, because we can not tell for sure that the DNS Zone of the Server’s FQDN is on the same server, so we could add that record.
I think that alias should be optional, because it is causing problems when trying to get a Let’s Encrypt Certificate. The user/admin needs to delete that alias before they can get a Let’s Encrypt Certificate for the domain.