I had already mentioned this situation before regarding the default DNS records created by Enhance, and after reviewing the issue in more detail, I identified several limitations that make DNS management less efficient and not fully aligned with best practices recommended in the RFCs and by diagnostic tools such as DNSInspect, IntoDNS or Zonemaster.
The first limitation is the inability to edit the global SOA record. At the moment, it is not possible to customise MNAME, RNAME, Refresh, Retry, Expire, Minimum TTL or even the SOA TTL itself. Enhance enforces fixed values that do not always meet recommended standards, such as Expire being set to 86400 when the recommended range is 604800 to 1209600, or Minimum TTL being set to 1400 when the recommended range is 3600 to 86400. This forces manual edits on every single domain, which becomes unmanageable in environments with many domains. A configurable global SOA template would be essential.
Another issue is the automatic creation of several DNS records that do not necessarily make sense for every provider. Some providers do not offer email services, so Enhance should allow the DNS template to define whether the MX record for the main domain should be created or not. Additionally, the panel automatically creates CNAME records such as imap, pop, smtp, ftp and mysql even when these services are not enabled or used. It would be much more appropriate if IMAP, POP, SMTP and similar records were created only optionally in the template and only when the email service is actually active. The FTP record should only be created when FTP is enabled, not by default on all domains. MX records also should not be created automatically for subdomains unless the user explicitly chooses to do so.
A more flexible rule-based logic is needed, allowing the DNS template to define conditions such as: if email is active, create the corresponding records; if FTP is active, create the FTP record; if there is a dedicated database host, create the mysql record; otherwise, create nothing. This would allow DNS behaviour to match the needs of each Enhance installation.
Another important limitation is that even when the DNS template is updated, existing zones do not get updated automatically. This means template improvements do not propagate to previously created domains. A bulk update feature, with the ability to choose which records to update (for example, only SOA, only TTLs, or only MX), would be extremely valuable and would prevent a significant amount of manual work.
In summary, Enhance’s DNS system has a solid foundation, but it would greatly benefit from the ability to edit the global SOA, have precise control over which records are created automatically, support conditional rules per service, and apply template updates retroactively to existing zones. These improvements would bring Enhance in line with what other panels like cPanel, Plesk or DirectAdmin already offer, and would result in a more consistent, modern and technically robust DNS management system. I am available to help test or validate these improvements if the team decides to move forward with them.
