For Google cloud authentication, DNSControl requires a JSON ‘Service Account Key’ for your project. Newlines in the private key need to be replaced with
\n.Copy the full JSON object into your
creds.json like so:
client_email, are the only fields that are strictly required, but it is sometimes easier to just paste the entire json object in. Either way is fine.
name_server_set is optional and requires special permission from your TAM at Google in order to setup (See Name server sets below)
See the Activation section for some tips on obtaining these credentials.
This provider does not recognize any special metadata fields unique to google cloud dns.
Use this provider like any other DNS Provider:
Go to “API Manager > Credentials”, and create a new “Service Account Key”
creds.jsonunder the name of your gcloud provider.
If a domain does not exist in your Google Cloud DNS account, DNSControl
will not automatically add it with the
push command. You’ll need to do that via the
control panel manually or via the
This optional feature lets you pin domains to a set of GCLOUD name servers. The
nameServerSet field is exposed in their API but there is
currently no facility for creating a name server set. You need special permission from your technical account manager at Google and they
will enable it on your account, responding with a list of names to use in the
name_server_set field above.
name_server_setonly applies on
create-domainsat the moment. Additional work needs to be done to support it during