srsakib
Active Member
Hello,
I would like to request standardized, core-level DNSSEC support for Clientexec registrar modules.
DNSSEC is an important domain security feature, but Clientexec currently does not appear to provide a standard registrar-module interface or a common client-area interface for managing DNSSEC. As a result, registrar module developers must implement it as a custom feature, and DNSSEC availability and user experience can vary significantly between modules.
Interestingly, DNSSEC support already exists in the Clientexec Netim registrar module. The module’s feature list explicitly includes DNSSEC support:
github.com
This demonstrates that DNSSEC functionality can already be implemented within Clientexec. However, rather than keeping it as a registrar-specific custom implementation, it would be much more beneficial to make DNSSEC part of the standard Clientexec registrar framework.
A standardized implementation could include:
Competing billing and hosting automation platforms, particularly WHMCS, already provide DNSSEC management through supported registrar modules. In a competitive market, adding standardized DNSSEC support would make Clientexec a more complete and attractive solution for hosting companies, domain resellers and module developers.
Small but important missing domain management features can prevent providers from migrating away from their existing billing platform. Even when they prefer Clientexec in other areas, the absence of features such as DNSSEC and private nameserver management can make migration difficult.
Since DNSSEC has already been implemented in an existing Clientexec registrar module, I hope you will consider using that implementation as a reference and introducing a standard, core-supported DNSSEC framework for all registrar modules.
Thank you for considering this feature.
I would like to request standardized, core-level DNSSEC support for Clientexec registrar modules.
DNSSEC is an important domain security feature, but Clientexec currently does not appear to provide a standard registrar-module interface or a common client-area interface for managing DNSSEC. As a result, registrar module developers must implement it as a custom feature, and DNSSEC availability and user experience can vary significantly between modules.
Interestingly, DNSSEC support already exists in the Clientexec Netim registrar module. The module’s feature list explicitly includes DNSSEC support:
GitHub - clientexec/netim-registrar: Netim registrar plugin for the ClientExec hosting application
Netim registrar plugin for the ClientExec hosting application - clientexec/netim-registrar
github.com
This demonstrates that DNSSEC functionality can already be implemented within Clientexec. However, rather than keeping it as a registrar-specific custom implementation, it would be much more beneficial to make DNSSEC part of the standard Clientexec registrar framework.
A standardized implementation could include:
- Retrieving the current DNSSEC status
- Enabling and disabling DNSSEC
- Adding DS records
- Updating existing DS records
- Deleting DS records
- Supporting multiple DS records
- Supporting Key Tag, Algorithm, Digest Type and Digest values
- A standardized set of registrar module methods
- A common management interface in both the admin area and client area
- The ability for registrar modules to declare whether DNSSEC is supported
- A clear message when a registrar or TLD does not support DNSSEC
Competing billing and hosting automation platforms, particularly WHMCS, already provide DNSSEC management through supported registrar modules. In a competitive market, adding standardized DNSSEC support would make Clientexec a more complete and attractive solution for hosting companies, domain resellers and module developers.
Small but important missing domain management features can prevent providers from migrating away from their existing billing platform. Even when they prefer Clientexec in other areas, the absence of features such as DNSSEC and private nameserver management can make migration difficult.
Since DNSSEC has already been implemented in an existing Clientexec registrar module, I hope you will consider using that implementation as a reference and introducing a standard, core-supported DNSSEC framework for all registrar modules.
Thank you for considering this feature.