Manage DNS authorizations (original) (raw)
DNS authorizations let you prove ownership of domains for Google-managed certificates. When creating a Google-managed certificate, one or more DNS authorizations can be specified to use for provisioning and renewal.
This page describes how to create and manage DNS authorizations for use with Google-managed certificates.
For more information, seeDomain authorizations.
Create a DNS authorization
Roles required for this task
To perform this task, you must have one of the following IAM roles on the target Google Cloud project.
- Certificate Manager Editor role (
roles/certificatemanager.editor) - Certificate Manager Owner role (
roles/certificatemanager.owner)
For more information, see Roles and permissions.
A DNS authorization only covers a single domain name. You must create a separate DNS authorization for each domain name that you want to use with the target certificate.
If you're creating a DNS authorization for a wildcard certificate, such as *.myorg.example.com, configure the DNS authorization for the parent domain—for example,myorg.example.com.
To independently manage certificates across multiple projects, you can usePER_PROJECT_RECORD DNS authorization. Certificate Manager can handle issuing and managing certificates for each project independently within Google Cloud. DNS authorizations and certificates that you use within a project are self-contained and don't interact with those in other projects.
Console
You can create a DNS authorization or attach an existing DNS authorization when creating a certificate. For more information, seeCreate a Google-managed certificate referencing the DNS authorization.
gcloud
Depending on your requirements, you can create any of these two types of DNS authorizations: FIXED_RECORD or PER_PROJECT_RECORD. For more information, see DNS authorization.
FIXED_RECORD DNS authorization
To create a FIXED_RECORD DNS authorization, use the following gcloud certificate-manager dns-authorizations create command:
gcloud certificate-manager dns-authorizations create AUTHORIZATION_NAME
--domain="DOMAIN_NAME"
--type=[FIXED_RECORD]
[--location="LOCATION"]
Replace the following:
AUTHORIZATION_NAME: the name of the DNS authorization.DOMAIN_NAME: the name of the target domain for which you are creating this DNS authorization. The domain name must be a fully qualified domain name, such asmyorg.example.com.LOCATION: the target Google Cloud location where you create the DNS authorization.
After creating the FIXED_RECORD DNS authorization, verify it with thegcloud certificate-manager dns-authorizations describe command:
gcloud certificate-manager dns-authorizations describe AUTHORIZATION_NAME
The output is similar to the following. In the output, find thednsResourceRecord line and get the CNAME record (data,name, and type) to add to your DNS configuration.
createTime: '2022-01-14T13:35:00.258409106Z' dnsResourceRecord: data: 0e40fc77-a37d-4eb8-8fe1-eea2e18d12d9.4.authorize.certificatemanager.goog. name: _acme-challenge.myorg.example.com. type: CNAME domain: myorg.example.com name: projects/myProject/locations/global/dnsAuthorizations/myAuthorization updateTime: '2022-01-14T13:35:01.571086137Z'
PER_PROJECT_RECORD DNS authorization
To create a PER_PROJECT_RECORD DNS authorization, use the followinggcloud certificate-manager dns-authorizations create command:
gcloud certificate-manager dns-authorizations create AUTHORIZATION_NAME
--domain="DOMAIN_NAME"
--type=PER_PROJECT_RECORD
[--location="LOCATION"]
Replace the following:
AUTHORIZATION_NAME: the name of the DNS authorization.DOMAIN_NAME: the name of the target domain for which you are creating this DNS authorization. The domain name must be a fully qualified domain name, such asmyorg.example.com.LOCATION: the target Google Cloud location where you create the DNS authorization.
After creating the PER_PROJECT_RECORD DNS authorization, verify it with the gcloud certificate-manager dns-authorizations describe command:
gcloud certificate-manager dns-authorizations describe AUTHORIZATION_NAME
The output is similar to the following. In the output, find thednsResourceRecord section. Locate the CNAME record and add the record's details (data,name, and type) to your DNS configuration.
createTime: '2022-01-14T13:35:00.258409106Z' dnsResourceRecord: data: 0e40fc77-a37d-4eb8-8fe1-eea2e18d12d9.4.authorize.certificatemanager.goog. name: _acme-challenge_ujmmovf2vn55tgye.myorg.example.com type: CNAME domain: myorg.example.com name: projects/myProject/locations/global/dnsAuthorizations/myAuthorization updateTime: '2022-01-14T13:35:01.571086137Z'
Terraform
To create a DNS authorization, you can use agoogle_certificate_manager_dns_authorization resource.
To learn how to apply or remove a Terraform configuration, seeBasic Terraform commands.
API
To create a DNS authorization, make a POST request to the dnsAuthorizations.create method:
POST /v1/projects/PROJECT_ID/locations/LOCATION/dnsAuthorizations?dns_authorization_id=AUTHORIZATION_NAME { "domain": "DOMAIN_NAME", "type": "PER_PROJECT_RECORD" //optional }
Replace the following:
PROJECT_ID: ID of your Google Cloud project.LOCATION: the target Google Cloud location where you create the DNS authorization. For the global location, useglobal.AUTHORIZATION_NAME: the name of the DNS authorization.DOMAIN_NAME: the name of the target domain for which you are creating this DNS authorization. The domain name must be a fully qualified domain name, such asmyorg.example.com.
Add the CNAME record to your DNS configuration
If you're using a third-party DNS solution to manage your DNS, refer to its documentation to add the CNAME record to the DNS configuration. If you're using Google Cloud to manage your DNS, complete the steps in this section.
Console
To create a record set, follow these steps:
- In the Google Cloud console, go to the DNS zones page.
Go to Cloud DNS zones - Click the name of the DNS zone where you want to add the record.
- On the Zone details page, click Add standard.
- On the Create record set page, in the DNS name field, enter the subdomain of the DNS zone.
When entering the subdomain name, make sure that the subdomain name, including the greyed-out text displayed in the DNS name field, matches the full value of thednsResourceRecord.namefield as displayed in the output of thegcloud certificate-manager dns-authorizations describe command.
See the following examples:- If the
dnsResourceRecord.namefield value is_acme-challenge.myorg.example.com., and the greyed-out text in theDNS name field is.example.com., then enter_acme-challenge.myorg. - If the
dnsResourceRecord.namefield value is_acme-challenge.myorg.example.com., and the greyed-out text in theDNS name field is.myorg.example.com., then enter_acme-challenge. - If the value of the
dnsResourceRecord.namefield is_acme-challenge_ujmmovf2vn55tgye.myorg.example.com., and the greyed-out text in the DNS name field is.myorg.example.com., then enter_acme-challenge_ujmmovf2vn55tgye.
- If the
- In the Resource record type field, select CNAME.
- In the TTL field, enter a positive numeric value for the resource record's time to live, which is the amount of time that it can be cached.
- From the TTL unit list, select the unit of time—for example,
30 minutes. - In the Canonical name field, enter the full value of the
dnsResourceRecord.datafield as displayed in the output of the gcloud certificate-manager dns-authorizations describe command. - To enter additional information, click Add item.
- Click Create.
gcloud
When you create a DNS authorization, the gcloud CLI command returns the corresponding CNAME record. To add the CNAME record to your DNS configuration in the DNS zone of the target domain, follow these steps:
- Initiate the DNS record transaction:
gcloud dns record-sets transaction start --zone="DNS_ZONE_NAME"
ReplaceDNS_ZONE_NAMEwith the name of the target DNS zone. - Add the CNAME record to the target DNS zone:
gcloud dns record-sets transaction add CNAME_RECORD \
--name="VALIDATION_SUBDOMAIN_NAME.DOMAIN_NAME." \
--ttl="30" \
--type="CNAME" \
--zone="DNS_ZONE_NAME"
Replace the following:CNAME_RECORD: the full data value of the CNAME record returned by the Google Cloud CLI command that created the corresponding DNS authorization.VALIDATION_SUBDOMAIN_NAME: the prefix subdomain of the DNS zone, such as_acme-challenge. You can copy the name from thegcloud certificate-manager dns-authorizations describecommand log, as described in Create a DNS authorization.DOMAIN_NAME: the name of the target domain.The domain name must be a fully qualified domain name, such asmyorg.example.com. You must also include the trailing period after the target domain name.DNS_ZONE_NAME: the name of the target DNS zone.
For more information about the difference betweenFIXED_RECORDandPER_PROJECT_RECORDDNS authorizations, see the following examples. The only difference between the two examples is the value of the--nameflag.
FIXED_RECORD DNS authorization
gcloud dns record-sets transaction add 0e40fc77-a37d-4eb8-8fe1-eea2e18d12d9.4.authorize.certificatemanager.goog. \
--name="_acme-challenge.myorg.example.com." \
--ttl="30" \
--type="CNAME" \
--zone="myorg-example-com"
PER_PROJECT_RECORD DNS authorization
gcloud dns record-sets transaction add 0e40fc77-a37d-4eb8-8fe1-eea2e18d12d9.4.authorize.certificatemanager.goog. \
--name="_acme-challenge_ujmmovf2vn55tgye.myorg.example.com." \
--ttl="30" \
--type="CNAME" \
--zone="myorg-example-com"
- Run the DNS record transaction to save your changes:
gcloud dns record-sets transaction execute --zone="DNS_ZONE_NAME"
ReplaceDNS_ZONE_NAMEwith the name of the target DNS zone.
Terraform
To add the CNAME record to your DNS configuration, you can use agoogle_dns_record_set resource.
When you update a DNS authorization, you can do the following:
- Specify new labels
- Specify a new description
Roles required for this task
To perform this task, you must have one of the following IAM roles on the target Google Cloud project.
- Certificate Manager Editor role (
roles/certificatemanager.editor) - Certificate Manager Owner role (
roles/certificatemanager.owner)
For more information, see Roles and permissions.
gcloud
To update a DNS authorization, use the certificate-manager dns-authorizations updatecommand:
gcloud certificate-manager dns-authorizations update AUTHORIZATION_NAME
[--update-labels="LABELS"]
[--description="DESCRIPTION"]
[--location="LOCATION"]
Replace the following:
AUTHORIZATION_NAME: the name of the DNS authorization.LABELS: labels for this DNS authorization. This flag is optional.DESCRIPTION: description for this DNS authorization. This flag is optional.LOCATION: the target Google Cloud location. The default location isglobal.
API
Update a DNS authorization by making a PATCH request to thednsAuthorizations.patch method as follows:
PATCH /v1/projects/PROJECT_ID/locations/LOCATION/dnsAuthorizations/AUTHORIZATION_NAME?updateMask=labels,description { description: "DESCRIPTION", labels: { "LABEL_KEY": "LABEL_VALUE" } }
Replace the following:
PROJECT_ID: ID of your Google Cloud project.LOCATION: the target Google Cloud location. The default location isglobal.AUTHORIZATION_NAME: the name of the DNS authorization.DESCRIPTION: an optional field that specifies the description for this DNS authorization.LABEL_KEY: a label key applied to this DNS authorization.LABEL_VALUE: a label value applied to this DNS authorization.
You can see all DNS authorizations in your project and their details.
Roles required for this task
To perform this task, you must have one of the following IAM roles on the target Google Cloud project.
- Certificate Manager Viewer role (
roles/certificatemanager.viewer) - Certificate Manager Editor role (
roles/certificatemanager.editor) - Certificate Manager Owner role (
roles/certificatemanager.owner)
For more information, see Roles and permissions.
gcloud
To list DNS authorizations, use the certificate-manager dns-authorizations listcommand:
gcloud certificate-manager dns-authorizations list
--filter="FILTER"
--page-size="PAGE_SIZE"
--limit="LIMIT"
--sort-by="SORT_BY"
[--location="LOCATION"]
Replace the following:
FILTER: an expression that constrains the returned results to specific values.
For example, you can filter results by the following criteria:- Domain:
--filter='domain=myorg.example.com' - Labels and creation time:
--filter='labels.key:value AND create_time > "2021-09-01T00:00:00Z"'
For more filtering examples that you can use with Certificate Manager, see Sorting and filtering list resultsin the Cloud Key Management Service documentation.
- Domain:
PAGE_SIZE: number of results that you want to return per pageLIMIT: maximum number of results that you want to returnSORT_BY: a comma-separated list ofnamefields by which the returned results are sorted. The default sort order is ascending; for descending sort order, prefix the field with a tilde (~).LOCATION: the target Google Cloud location. To list DNS authorizations from all regions, use-as the value. The default is-. This flag is optional.
API
List all configured DNS authorizations by making a GET request to the dnsAuthorizations.list method as follows:
GET /v1/projects/PROJECT_ID/locations/LOCATION/dnsAuthorizations?filter=FILTER&pageSize=PAGE_SIZE&sortBy=SORT_BY
Replace the following:
PROJECT_ID: ID of your Google Cloud project.LOCATION: the target Google Cloud location. To see all DNS authorizations across all locations, specify a single hyphen (-).FILTER: an expression that constrains the returned results to specific values.
For example, you can filter results by the following criteria:- Domain:
--filter='domain=myorg.example.com' - Labels and creation time:
--filter='labels.key:value AND create_time > "2021-09-01T00:00:00Z"'
- Domain:
PAGE_SIZE: number of results that you want to return per pageSORT_BY: a comma-separated list ofnamefields by which the returned results are sorted. The default sort order is ascending; for descending sort order, prefix the field with a tilde (~).
Delete a DNS authorization
To delete a DNS authorization that is assigned to Google-managed certificates,delete the certificatesbefore you delete the DNS authorization.
Roles required for this task
To perform this task, you must have one of the following IAM roles on the target Google Cloud project.
- Certificate Manager Owner role (
roles/certificatemanager.owner)
For more information, see Roles and permissions.
gcloud
To delete a DNS authorization, use the certificate-manager dns-authorizations deletecommand:
gcloud certificate-manager dns-authorizations delete AUTHORIZATION_NAME
[--location="LOCATION"]
Replace the following:
AUTHORIZATION_NAME: the name of the DNS authorization.LOCATION: the target Google Cloud location. The default location isglobal.
API
Delete a DNS authorization by making a DELETE request to thednsAuthorizations.delete method as follows:
DELETE /v1/projects/PROJECT_ID/locations/LOCATION/dnsAuthorizations/AUTHORIZATION_NAME
Replace the following:
PROJECT_ID: ID of your Google Cloud project.LOCATION: the target Google Cloud location. The default location isglobal.AUTHORIZATION_NAME: the name of the DNS authorization.