Domain Limit Module Optimizations
Enabling the "domain limits" option in ISPConfig leads to some issues and inconsistencies in the handling of subdomains which I want to address in this feature request:
- Clients cannot create "real/standalone" websites for freely chosen subdomains, and they also cannot create aliasdomains for freely chosen subdomains. The admin would have to assign each subdomain to the client manually. I think this is a real showstopper for companies with many clients, and quite "anit automation". The client has to contact the admin (if he even is aware of the option), and the admin has to quickly respond. Not a really smooth workflow.
- The client can still create subdomains via the "Subdomain" and "Subdomain (vHost)" options. This makes the domain limits function a bit inconsistent, because clients can "partially" work with subdomains. So as an admin, you can't really stop them from creating subdomains, but they can still not fully use them (e.g. real/standalone websites, aliasdomains).
- Until now (without the domain limits enabled) we encouraged users to create subdomains as real/standalone websites if they are not tightly linked to the website of the root domain, because it leads to a cleaner and more logical separation, and it also allows them to individually backup/restore said websites. This is not possible at the moment, and the workaround with Subdomain (vHost) websites doesn't lead to a clean separation of websites.
- In the "create new wesite" and "create new aliasdomain" forms, add an (optional) freetext-field "Host" or "Subdomain", just like in the "create new subdomain" form. That way, users can create subdomain-websites and subdomain-aliaswebsites, but only for the domains which were assigned to them, which is the ideal usecase of the domain limit module in my opinion.