Supported provider
DNSimple DNS, in the same place as everything else.
Does DNSMentor support DNSimple?
Yes. DNSMentor manages DNSimple DNS through its API, showing its zones alongside the other 25 supported providers in a single estate view. Every DNSimple change goes through the same 56 pre-flight checks, approval policy, independent verification and tamper-evident audit trail as every other provider.
Connecting DNSimple
- Create the credential in DNSimple The numeric account id, not the account name. It is the number in the DNSimple app URL — https://dnsimple.com/a/1234/domains means 1234. It is also returned by GET /v2/whoami. Every API path is scoped to it, and a wrong value fails as 'zone not found' rather than as an authentication error.
- Add the connection in DNSMentor Go to Admin → Providers & API keys, choose DNSimple, and paste the credential. DNSMentor stores it encrypted and strips it from every log and export.
- Sync the estate DNSMentor discovers every zone the DNSimple 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 DNSimple asks you for
The exact fields DNSMentor needs, and where in DNSimple to create them. Every secret is encrypted at rest and stripped by name from logs, exports and the audit trail.
Account ID not secret The numeric account id, not the account name. It is the number in the DNSimple app URL — https://dnsimple.com/a/1234/domains means 1234. It is also returned by GET /v2/whoami. Every API path is scoped to it, and a wrong value fails as 'zone not found' rather than as an authentication error.
API Access Token secret DNSimple → Account → Automation → API tokens → New account token. Use an ACCOUNT token, not a user token: a user token reaches every account the person can see, so it would let one connection edit another customer's zones. DNSimple tokens carry full read/write access to the account — there is no DNS-only or read-only scope — and revoking one breaks every integration using it.
The sharp edge in DNSimple's API
Every provider API has one behaviour that catches integrations out. This is DNSimple's, and DNSMentor's adapter is written around it — the sort of thing you would otherwise discover during a migration.
What you get on top of the DNSimple console
One estate, not one provider
DNSimple 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 DNSimple 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.
DNSimple questions
Can I manage DNSimple DNS alongside my other providers?
Yes. DNSMentor connects DNSimple 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 DNSimple?
DNSMentor needs Account ID, API Access Token for DNSimple. The numeric account id, not the account name. It is the number in the DNSimple app URL — https://dnsimple.com/a/1234/domains means 1234. It is also returned by GET /v2/whoami. Every API path is scoped to it, and a wrong value fails as 'zone not found' rather than as an authentication error.
Does DNSMentor move my zones away from DNSimple?
No. Your zones stay hosted at DNSimple and remain authoritative there. DNSMentor reads and writes through the DNSimple 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 DNSimple 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 DNSimple API after re-reading live state, and independently verified in public DNS afterwards.
Other providers DNSMentor manages
Connect DNSimple 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