Supported provider
Gandi LiveDNS DNS, in the same place as everything else.
Does DNSMentor support Gandi LiveDNS?
Yes. DNSMentor manages Gandi LiveDNS DNS through its API, showing its zones alongside the other 25 supported providers in a single estate view. Every Gandi LiveDNS change goes through the same 56 pre-flight checks, approval policy, independent verification and tamper-evident audit trail as every other provider.
Connecting Gandi LiveDNS
- Create the credential in Gandi LiveDNS Gandi Admin → your organisation → Settings → Personal Access Token (https://admin.gandi.net/organizations/account/pat) → Create a token. Give it the 'Manage domain name technical configurations' permission and restrict it to the domains this connection should manage. A token belongs to one organisation, so an MSP holding domains across several Gandi organisations needs one connection per organisation. Do not use the older API key from account.gandi.net: it is deprecated, it cannot be scoped, and it carries every permission its owner has.
- Add the connection in DNSMentor Go to Admin → Providers & API keys, choose Gandi LiveDNS, and paste the credential. DNSMentor stores it encrypted and strips it from every log and export.
- Sync the estate DNSMentor discovers every zone the Gandi LiveDNS 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 Gandi LiveDNS asks you for
The exact fields DNSMentor needs, and where in Gandi LiveDNS to create them. Every secret is encrypted at rest and stripped by name from logs, exports and the audit trail.
Personal Access Token secret Gandi Admin → your organisation → Settings → Personal Access Token (https://admin.gandi.net/organizations/account/pat) → Create a token. Give it the 'Manage domain name technical configurations' permission and restrict it to the domains this connection should manage. A token belongs to one organisation, so an MSP holding domains across several Gandi organisations needs one connection per organisation. Do not use the older API key from account.gandi.net: it is deprecated, it cannot be scoped, and it carries every permission its owner has.
Organisation ID not secret Only needed when the token's account can see more than one organisation and you want this connection limited to one of them. Gandi Admin → Organisations → the organisation → the UUID in the browser's address bar. Leave blank to see every domain the token can reach.
The sharp edge in Gandi LiveDNS's API
Every provider API has one behaviour that catches integrations out. This is Gandi LiveDNS'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 Gandi LiveDNS console
One estate, not one provider
Gandi LiveDNS 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 Gandi LiveDNS 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.
Gandi LiveDNS questions
Can I manage Gandi LiveDNS DNS alongside my other providers?
Yes. DNSMentor connects Gandi LiveDNS 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 Gandi LiveDNS?
DNSMentor needs Personal Access Token, Organisation ID for Gandi LiveDNS. Gandi Admin → your organisation → Settings → Personal Access Token (https://admin.gandi.net/organizations/account/pat) → Create a token. Give it the 'Manage domain name technical configurations' permission and restrict it to the domains this connection should manage. A token belongs to one organisation, so an MSP holding domains across several Gandi organisations needs one connection per organisation. Do not use the older API key from account.gandi.net: it is deprecated, it cannot be scoped, and it carries every permission its owner has.
Does DNSMentor move my zones away from Gandi LiveDNS?
No. Your zones stay hosted at Gandi LiveDNS and remain authoritative there. DNSMentor reads and writes through the Gandi LiveDNS 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 Gandi LiveDNS 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 Gandi LiveDNS API after re-reading live state, and independently verified in public DNS afterwards.
Other providers DNSMentor manages
Connect Gandi LiveDNS 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