Automate Google Cloud DNS

What HumDay can do in Google Cloud DNS

23 documented operations change something in Google Cloud DNS.

• POSTGets the access control policy for a resource./dns/v2/{resource}:getIamPolicy
• POSTSets the access control policy on the specified resource./dns/v2/{resource}:setIamPolicy
• POSTCreates a new Policy./dns/v2/projects/{project}/locations/{location}/policies
• POSTCreates a new ManagedZone./dns/v2/projects/{project}/locations/{location}/managedZones
• POSTReturns permissions that a caller has on the specified resource./dns/v2/{resource}:testIamPermissions
• POSTCreates a new Response Policy/dns/v2/projects/{project}/locations/{location}/responsePolicies
• POSTCreates a new ResourceRecordSet./dns/v2/projects/{project}/locations/{location}/managedZones/{managedZone}/rrsets
• POSTCreates a new Response Policy Rule./dns/v2/projects/{project}/locations/{location}/responsePolicies/{responsePolicy}/rules
• DELETEDeletes a previously created Policy./dns/v2/projects/{project}/locations/{location}/policies/{policy}
• PATCHApplies a partial update to an existing Policy./dns/v2/projects/{project}/locations/{location}/policies/{policy}
• PUTUpdates an existing Policy./dns/v2/projects/{project}/locations/{location}/policies/{policy}
• DELETEDeletes a previously created ManagedZone./dns/v2/projects/{project}/locations/{location}/managedZones/{managedZone}
• PATCHApplies a partial update to an existing ManagedZone./dns/v2/projects/{project}/locations/{location}/managedZones/{managedZone}
• PUTUpdates an existing ManagedZone./dns/v2/projects/{project}/locations/{location}/managedZones/{managedZone}
• DELETEDeletes a previously created Response Policy./dns/v2/projects/{project}/locations/{location}/responsePolicies/{responsePolicy}
• PATCHApplies a partial update to an existing Response Policy./dns/v2/projects/{project}/locations/{location}/responsePolicies/{responsePolicy}
• PUTUpdates an existing Response Policy./dns/v2/projects/{project}/locations/{location}/responsePolicies/{responsePolicy}
• POSTAtomically updates the ResourceRecordSet collection./dns/v2/projects/{project}/locations/{location}/managedZones/{managedZone}/changes
• DELETEDeletes a previously created Response Policy Rule./dns/v2/projects/{project}/locations/{location}/responsePolicies/{responsePolicy}/rules/{responsePolicyRule}
• PATCHApplies a partial update to an existing Response Policy Rule./dns/v2/projects/{project}/locations/{location}/responsePolicies/{responsePolicy}/rules/{responsePolicyRule}
• PUTUpdates an existing Response Policy Rule./dns/v2/projects/{project}/locations/{location}/responsePolicies/{responsePolicy}/rules/{responsePolicyRule}
• DELETEDeletes a previously created ResourceRecordSet./dns/v2/projects/{project}/locations/{location}/managedZones/{managedZone}/rrsets/{name}/{type}
• PATCHApplies a partial update to an existing ResourceRecordSet./dns/v2/projects/{project}/locations/{location}/managedZones/{managedZone}/rrsets/{name}/{type}

What HumDay can read from Google Cloud DNS

These are the operations a schedule or a trigger can watch.

• GETFetches the representation of an existing Project./dns/v2/projects/{project}/locations/{location}
• GETEnumerates all Policies associated with a project./dns/v2/projects/{project}/locations/{location}/policies
• GETEnumerates ManagedZones that have been created but not yet deleted./dns/v2/projects/{project}/locations/{location}/managedZones
• GETEnumerates all Response Policies associated with a project./dns/v2/projects/{project}/locations/{location}/responsePolicies
• GETFetches the representation of an existing Policy./dns/v2/projects/{project}/locations/{location}/policies/{policy}
• GETFetches the representation of an existing ManagedZone./dns/v2/projects/{project}/locations/{location}/managedZones/{managedZone}
• GETFetches the representation of an existing Response Policy./dns/v2/projects/{project}/locations/{location}/responsePolicies/{responsePolicy}
• GETEnumerates ResourceRecordSets that you have created but not yet deleted./dns/v2/projects/{project}/locations/{location}/managedZones/{managedZone}/rrsets
• GETEnumerates Changes to a ResourceRecordSet collection./dns/v2/projects/{project}/locations/{location}/managedZones/{managedZone}/changes
• GETEnumerates DnsKeys to a ResourceRecordSet collection./dns/v2/projects/{project}/locations/{location}/managedZones/{managedZone}/dnsKeys
• GETEnumerates Operations for the given ManagedZone./dns/v2/projects/{project}/locations/{location}/managedZones/{managedZone}/operations
• GETEnumerates all Response Policy Rules associated with a project./dns/v2/projects/{project}/locations/{location}/responsePolicies/{responsePolicy}/rules
• GETFetches the representation of an existing Change./dns/v2/projects/{project}/locations/{location}/managedZones/{managedZone}/changes/{changeId}
• GETFetches the representation of an existing DnsKey./dns/v2/projects/{project}/locations/{location}/managedZones/{managedZone}/dnsKeys/{dnsKeyId}
• GETFetches the representation of an existing Operation./dns/v2/projects/{project}/locations/{location}/managedZones/{managedZone}/operations/{operation}
• GETFetches the representation of an existing Response Policy Rule./dns/v2/projects/{project}/locations/{location}/responsePolicies/{responsePolicy}/rules/{responsePolicyRule}
• GETFetches the representation of an existing ResourceRecordSet./dns/v2/projects/{project}/locations/{location}/managedZones/{managedZone}/rrsets/{name}/{type}

How automating Google Cloud DNS works

1. Describe the outcome. Say what you want to happen, in your own words. No node graphs, no field mapping.
2. Approve the contract. HumDay writes down exactly what it will do, what it will touch, and what it will never do. You approve it before anything is built.
3. See it proven. The program runs and shows you the result before it is allowed near your live Google Cloud DNS account.
4. Grant access, then go live. You approve the specific Google Cloud DNS operations it may use — and only those.

Automate Google Cloud DNS with these

• Gmail79 operations
• Google+9 operations
• Google Abusive Experience Report2 operations
• Google Accelerated Mobile Pages (AMP) URL1 operations
• Google Access Approval7 operations
• Google Access Context Manager9 operations
• Google ACME DNS2 operations
• Google Ad Exchange Buyer38 operations
• Google Ad Exchange Buyer II50 operations
• Google Ad Experience Report2 operations
• Google Admin SDK122 operations
• Google AdMob7 operations

Categories

• Analytics
• Media

Questions about Google Cloud DNS automation

Can HumDay connect to Google Cloud DNS?

Yes. HumDay reads Google Cloud DNS's own published API description and derives the operations from it, so there is no hand-built connector to wait for. 40 operations are documented.

Do I need to write code to automate Google Cloud DNS?

No. You describe the outcome you want in plain words. HumDay agrees a contract with you, writes the program, and shows you a test run before anything touches your Google Cloud DNS account.

What can HumDay do in Google Cloud DNS?

23 of the 40 documented operations change something in Google Cloud DNS, and 17 read from it. HumDay only ever uses the specific operations your approved contract needs.

Is my Google Cloud DNS account safe?

Your credentials are stored encrypted and are never shown in chat, code, or logs. Every run is limited to the operations you explicitly approved, and anything that writes to Google Cloud DNS is held behind that approval.

Where this came from

The operations above are read from a published API description for Google Cloud DNS at dns.googleapis.com/$discovery/rest?version=v2. Descriptions are the provider’s own words, not ours. Last published 2023-04-07.