Supported provider
ClouDNS DNS, in the same place as everything else.
Does DNSMentor support ClouDNS?
Yes. DNSMentor manages ClouDNS DNS through its API, showing its zones alongside the other 25 supported providers in a single estate view. Every ClouDNS change goes through the same 56 pre-flight checks, approval policy, independent verification and tamper-evident audit trail as every other provider.
Connecting ClouDNS
- Create the credential in ClouDNS Your ClouDNS API user ID. Use this for a full API user.
- Add the connection in DNSMentor Go to Admin → Providers & API keys, choose ClouDNS, and paste the credential. DNSMentor stores it encrypted and strips it from every log and export.
- Sync the estate DNSMentor discovers every zone the ClouDNS account holds and imports every record in them. This is a read operation — nothing is written to any zone.
- Group by client and start working Assign the imported domains to client portfolios, and the estate view, health scoring, checks and audit trail apply from that point on.
What ClouDNS asks you for
The exact fields DNSMentor needs, and where in ClouDNS to create them. Every secret is encrypted at rest and stripped by name from logs, exports and the audit trail.
Auth ID not secret Your ClouDNS API user ID. Use this for a full API user.
Sub Auth ID not secret Use instead of Auth ID when connecting as an API sub-user.
Sub Auth User not secret Use instead of Auth ID when your sub-user has a custom username.
Auth Password secret ClouDNS control panel → API settings. Sub-users can be restricted to read-only, which will fail at write time rather than when the connection is tested.
What you get on top of the ClouDNS console
One estate, not one provider
ClouDNS zones sit beside every other provider your clients came with, grouped by the client who pays for them and searchable in one place.
56 checks before apply
The ClouDNS console will accept a second SPF record or an MX pointing at an address without comment. DNSMentor will not.
Approval and audit
A second pair of eyes where policy requires it, and a hash-chained record of who changed what — neither of which a provider console offers.
ClouDNS questions
Can I manage ClouDNS DNS alongside my other providers?
Yes. DNSMentor connects ClouDNS through its API and shows its zones in the same estate view as every other provider you connect — 26 are supported in total. Your engineers work in one interface instead of switching between provider portals, and the same checks, approval policy and audit trail apply regardless of which provider a domain happens to be with.
What credentials does DNSMentor need for ClouDNS?
DNSMentor needs Auth ID, Sub Auth ID, Sub Auth User, Auth Password for ClouDNS. Your ClouDNS API user ID. Use this for a full API user.
Does DNSMentor move my zones away from ClouDNS?
No. Your zones stay hosted at ClouDNS and remain authoritative there. DNSMentor reads and writes through the ClouDNS API, so nothing about your resolution path changes, and if you stop using DNSMentor the zones carry on exactly as they are.
Does DNSMentor validate ClouDNS changes before applying them?
Yes. All 56 checks run against the zone as it would exist after the change, whichever provider hosts it. The change is then simulated, routed for approval if policy requires it, written through the ClouDNS API after re-reading live state, and independently verified in public DNS afterwards.
Other providers DNSMentor manages
Connect ClouDNS in about five minutes.
Paste one credential, sync, and see every zone in that account. It is a read operation — nothing is written until somebody presses apply.
No card. No trial clock. UK-hosted, and we will tell you which providers we have actually proven before you ask.
Last updated