Supported provider
Linode DNS, in the same place as everything else.
Does DNSMentor support Linode?
Yes. DNSMentor manages Linode DNS through its API, showing its zones alongside the other 25 supported providers in a single estate view. Every Linode change goes through the same 56 pre-flight checks, approval policy, independent verification and tamper-evident audit trail as every other provider.
Connecting Linode
- Create the credential in Linode Linode Cloud Manager → your username (top right) → API Tokens → Create a Personal Access Token. Set every scope to 'None' except Domains, which must be 'Read/Write'; the token then cannot touch Linodes, billing or account settings. Give it an expiry and a label naming this DNSMentor connection, because Linode shows the token value once and never again. Linode tokens cannot be restricted to particular domains or to a source IP address, so this credential can edit DNS for every domain on the account.
- Add the connection in DNSMentor Go to Admin → Providers & API keys, choose Linode, and paste the credential. DNSMentor stores it encrypted and strips it from every log and export.
- Sync the estate DNSMentor discovers every zone the Linode 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 Linode asks you for
The exact fields DNSMentor needs, and where in Linode to create them. Every secret is encrypted at rest and stripped by name from logs, exports and the audit trail.
Personal Access Token secret Linode Cloud Manager → your username (top right) → API Tokens → Create a Personal Access Token. Set every scope to 'None' except Domains, which must be 'Read/Write'; the token then cannot touch Linodes, billing or account settings. Give it an expiry and a label naming this DNSMentor connection, because Linode shows the token value once and never again. Linode tokens cannot be restricted to particular domains or to a source IP address, so this credential can edit DNS for every domain on the account.
The sharp edge in Linode's API
Every provider API has one behaviour that catches integrations out. This is Linode'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 Linode console
One estate, not one provider
Linode 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 Linode 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.
Linode questions
Can I manage Linode DNS alongside my other providers?
Yes. DNSMentor connects Linode 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 Linode?
DNSMentor needs Personal Access Token for Linode. Linode Cloud Manager → your username (top right) → API Tokens → Create a Personal Access Token. Set every scope to 'None' except Domains, which must be 'Read/Write'; the token then cannot touch Linodes, billing or account settings. Give it an expiry and a label naming this DNSMentor connection, because Linode shows the token value once and never again. Linode tokens cannot be restricted to particular domains or to a source IP address, so this credential can edit DNS for every domain on the account.
Does DNSMentor move my zones away from Linode?
No. Your zones stay hosted at Linode and remain authoritative there. DNSMentor reads and writes through the Linode 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 Linode 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 Linode API after re-reading live state, and independently verified in public DNS afterwards.
Other providers DNSMentor manages
Connect Linode 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