srsakib
Active Member
Hello,
I would like to request native support for child nameservers, also known as private nameservers or nameserver glue records, within Clientexec registrar modules.
Currently, Clientexec supports standard domain nameserver updates, but it does not appear to provide built-in registrar module functionality for managing child nameservers, including:
Competing billing platforms, such as WHMCS, already provide support for private nameserver and child nameserver management. Adding similar functionality would therefore be a valuable competitive advantage for Clientexec.
In a competitive billing and hosting automation market, small but essential features like this can strongly influence platform adoption. When several important registrar functions are missing, many hosting providers become hesitant to migrate from their existing billing platform, even when they otherwise prefer Clientexec.
It would be helpful if Clientexec could introduce standardized registrar module methods and customer-facing controls for child nameserver management, similar to the existing domain contact, DNS, and nameserver management features.
Please consider adding this functionality in a future Clientexec release. It would improve registrar integration capabilities and make Clientexec a more complete and competitive solution for hosting providers.
Thank you.
I would like to request native support for child nameservers, also known as private nameservers or nameserver glue records, within Clientexec registrar modules.
Currently, Clientexec supports standard domain nameserver updates, but it does not appear to provide built-in registrar module functionality for managing child nameservers, including:
- Registering a private nameserver, such as ns1.example.com
- Assigning or updating its IP address
- Modifying an existing child nameserver
- Deleting a child nameserver
- Managing both IPv4 and IPv6 glue records
Competing billing platforms, such as WHMCS, already provide support for private nameserver and child nameserver management. Adding similar functionality would therefore be a valuable competitive advantage for Clientexec.
In a competitive billing and hosting automation market, small but essential features like this can strongly influence platform adoption. When several important registrar functions are missing, many hosting providers become hesitant to migrate from their existing billing platform, even when they otherwise prefer Clientexec.
It would be helpful if Clientexec could introduce standardized registrar module methods and customer-facing controls for child nameserver management, similar to the existing domain contact, DNS, and nameserver management features.
Please consider adding this functionality in a future Clientexec release. It would improve registrar integration capabilities and make Clientexec a more complete and competitive solution for hosting providers.
Thank you.