Supported provider
Google Cloud DNS DNS, in the same place as everything else.
Does DNSMentor support Google Cloud DNS?
Yes. DNSMentor manages Google Cloud DNS DNS through its API, showing its zones alongside the other 25 supported providers in a single estate view. Every Google Cloud DNS change goes through the same 56 pre-flight checks, approval policy, independent verification and tamper-evident audit trail as every other provider.
Connecting Google Cloud DNS
- Create the credential in Google Cloud DNS Google Cloud console → IAM & Admin → Service Accounts → pick or create the account → Keys → Add key → Create new key → JSON. Paste the whole downloaded file, braces included. Grant that service account the DNS Administrator role (roles/dns.admin) on the project holding the zones, or DNS Reader (roles/dns.reader) if you only want DNSMentor to read. Google shows the private key once and cannot show it again, so if the file has been lost, create a second key rather than hunting for the first.
- Add the connection in DNSMentor Go to Admin → Providers & API keys, choose Google Cloud DNS, and paste the credential. DNSMentor stores it encrypted and strips it from every log and export.
- Sync the estate DNSMentor discovers every zone the Google Cloud DNS 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 Google Cloud DNS asks you for
The exact fields DNSMentor needs, and where in Google Cloud DNS to create them. Every secret is encrypted at rest and stripped by name from logs, exports and the audit trail.
Service account key (JSON) secret Google Cloud console → IAM & Admin → Service Accounts → pick or create the account → Keys → Add key → Create new key → JSON. Paste the whole downloaded file, braces included. Grant that service account the DNS Administrator role (roles/dns.admin) on the project holding the zones, or DNS Reader (roles/dns.reader) if you only want DNSMentor to read. Google shows the private key once and cannot show it again, so if the file has been lost, create a second key rather than hunting for the first.
Project ID not secret Only needed when the zones live in a different project from the service account — otherwise leave this blank and the project_id inside the JSON is used. This is the project ID (lower-case, e.g. acme-dns-prod), not the project number or the display name.
The sharp edge in Google Cloud DNS's API
Every provider API has one behaviour that catches integrations out. This is Google Cloud DNS'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 Google Cloud DNS console
One estate, not one provider
Google Cloud DNS 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 Google Cloud DNS 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.
Google Cloud DNS questions
Can I manage Google Cloud DNS DNS alongside my other providers?
Yes. DNSMentor connects Google Cloud DNS 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 Google Cloud DNS?
DNSMentor needs Service account key (JSON), Project ID for Google Cloud DNS. Google Cloud console → IAM & Admin → Service Accounts → pick or create the account → Keys → Add key → Create new key → JSON. Paste the whole downloaded file, braces included. Grant that service account the DNS Administrator role (roles/dns.admin) on the project holding the zones, or DNS Reader (roles/dns.reader) if you only want DNSMentor to read. Google shows the private key once and cannot show it again, so if the file has been lost, create a second key rather than hunting for the first.
Does DNSMentor move my zones away from Google Cloud DNS?
No. Your zones stay hosted at Google Cloud DNS and remain authoritative there. DNSMentor reads and writes through the Google Cloud DNS 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 Google Cloud DNS 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 Google Cloud DNS API after re-reading live state, and independently verified in public DNS afterwards.
Other providers DNSMentor manages
Connect Google Cloud DNS 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