when a MX is not configured on a domain, for example because your bind import failed or your export was incomplete, you should get a warning about it, this is an item you could forget easy with high impact for your users.
We would love to see SSO integrations (for sure Microsoft, but maybe even others?) so we can apply our security and conditional access baseline for logging on to our CtrlDNS environment.
Implement a new API endpoint in ctrlDNS that returns a paginated list of all domains associated with the authenticated user’s profile. The endpoint must enforce access control so users only see domains they own or have access to.
As discussed, we are working on implementing WHMCS as our order and management system. We would like to integrate with that tool so we can provide our clients and partners with direct login to ctrlDNS, so they can manage their records via this system instead of directly through another DNS integration, because then we lose control and monitoring on changes etc. If DNS records could be displayed as read-only in WHMCS, that would be great. For making changes, a client should have an SSO login to ctrlDNS and land directly in the correct zone.
Noticed it wasn’t on the roadmap, but I we discussed it briefly yesterday. It would be great if we could manage one or more redirects via ctrlDNS (instead of via Cloudflare in our case).
It would be great if we could create specific templates that we can use: When creating a new zone When updating an existing zone We use several default applications in our environment that always require the same set of DNS records — for example, SendGrid or our email solution. If we could add this predefined set of records in one go, it would save a lot of time (of course, with a proper check to avoid overwriting existing records).
We would like to see the ‘Pending deletion’ of a zone visible at Realtime Register
Sharing 30 zones at once is not possible, for example, so a separate invitation must be sent for each zone and each invitation must be accepted separately.
We would like to see functionality that allows performing a audit across all DNS records within the zones associated with a profile. This scan should make it possible to detect specific conditions, such as: Domains without a DMARC record Useful for identifying domains that require proper email authentication policies. Domains without MX records These should either be configured with valid mail servers or explicitly set up with specific records to block email functionality. Domains containing a ‘localhost’ record To highlight potential misconfigurations or security risks.