DNS Management Limitation for DKIM and _domainkey Records (Workaround Not Scalable)

EEnos DNS management currently struggles with handling modern email authentication records, especially DKIM configurations required by providers like Google Workspace and Microsoft 365.

In real-world scenarios, administrators frequently need to add custom DNS records such as DKIM TXT records (for example google._domainkey), DKIM CNAME records (Microsoft 365 selector-based DKIM), SPF and DMARC TXT records, and provider-specific verification records.

However, the current behavior introduces several issues. DNS records added via the panel are sometimes not reflected in the actual zone. _domainkey records may not be properly handled or published. TXT values, especially long DKIM keys, may be ignored or incorrectly parsed. Manual changes in zone files can be overwritten by rebuild operations. There is no clear feedback whether a DNS record is actually active in BIND. Advanced use cases require direct SSH access and manual zone editing.

We previously received a suggestion to create a separate DNS zone as a workaround for managing DKIM and related records. While this approach may technically work, it introduces additional operational complexity and deviates from standard DNS management practices, where all records for a domain are expected to be managed within a single authoritative zone.

In real-world hosting environments, DKIM, SPF, DMARC, and other verification records must be handled reliably within the primary domain zone. Requiring separate zones as a workaround is not scalable and can lead to misconfigurations.

EEnos DNS system should fully support _domainkey records (TXT and CNAME), ensure all DNS records added via the panel are reliably written to the actual zone files, properly handle long TXT values such as DKIM keys, prevent silent failures, provide validation feedback if a record is invalid, ensure rebuild operations do not overwrite valid custom records, and offer an advanced or raw DNS mode for full control when needed.

This is important because DKIM, SPF, and DMARC are essential for email deliverability, modern email providers require precise DNS configurations, reliable DNS behavior is critical for hosting providers, it reduces dependency on SSH and manual intervention, and improves trust in the control panel.

This improvement would significantly enhance EEnos usability for real-world hosting and email infrastructure management.