Updated on 2025-11-06 GMT+08:00

Domain Name Service

IAM provides system-defined identity policies to define common actions supported by cloud services. You can also create custom identity policies using the actions supported by cloud services for more refined access control.

In addition to IAM, the Organizations service also provides Service Control Policies (SCPs) to set access control policies.

SCPs do not actually grant any permissions to an entity. They only set the permissions boundary for the entity. When SCPs are attached to an organizational unit (OU) or a member account, the SCPs do not directly grant permissions to that OU or member account. Instead, the SCPs only determine what permissions are available for that member account or those member accounts under that OU. The granted permissions can be applied only if they are allowed by the SCPs.

To learn more about how IAM is different from Organizations for access control, see How IAM Is Different from Organizations for Access Control?.

This section describes the elements used by IAM custom identity policies and Organizations SCPs. The elements include actions, resources, and conditions.

Actions

Actions are specific operations that are allowed or denied in an identity policy.

  • The Access Level column describes how the action is classified (List, Read, or Write). This classification helps you understand the level of access that an action grants when you use it in an identity policy.
  • The Resource Type column indicates whether the action supports resource-level permissions.
    • You can use a wildcard (*) to indicate all resource types. If this column is empty (-), the action does not support resource-level permissions and you must specify all resources ("*") in your identity policy statements.
    • If this column includes a resource type, you must specify the URN in the Resource element of your identity policy statements.
    • Required resources are marked with asterisks (*) in the table. If you specify a resource in a statement using this action, then it must be of this type.

    For details about the resource types defined by DNS, see Resources.

  • The Condition Key column contains keys that you can specify in the Condition element of an identity policy statement.
    • If the Resource Type column has values for an action, the condition key takes effect only for the listed resource types.
    • If the Resource Type column is empty (-) for an action, the condition key takes effect for all resources that action supports.
    • If the Condition Key column is empty (-) for an action, the action does not support any condition keys.

    For details about the condition keys defined by DNS, see Conditions.

  • The Alias column lists the policy actions that are configured in identity policies. With these actions, you can use APIs for policy-based authorization. For details, see Policies and Identity Policies.

The following table lists the actions that you can define in identity policy statements for DNS.

Table 1 Actions supported by DNS

Action

Description

Access Level

Resource Type (*: required)

Condition Key

Alias

dns:zone:list

Grants permission to list the zones.

List

zone *

-

-

-

dns:zone:create

Grants permission to create a zone.

Write

zone *

-

-

-

dns:zone:createBatchPublicZonesByName

Grants permission to create zones in batches.

Write

zone *

-

-

-

g:EnterpriseProjectId

dns:zone:get

Grants permission to obtain a zone.

Read

zone *

-

dns:zone:update

Grants permission to update a zone.

Write

zone *

-

dns:zone:delete

Grants permission to delete a zone.

Write

zone *

-

dns:zone:associaterouter

Grants permission to associate a VPC with a private zone.

Write

zone *

-

dns:zone:disassociaterouter

Grants permission to disassociate a VPC from a private zone.

Write

zone *

-

dns:zone:setProxyPattern

Grants permission to set recursive resolution proxy for private subdomains.

Write

zone *

-

dns:zone:transfer

Grants permission to transfer public domain names.

Write

zone *

-

dns:recordset:list

Grants permission to list the record sets.

List

zone *

-

dns:recordset:create

Grants permission to create a record set.

Write

zone *

-

-

dns:recordset:get

Grants permission to obtain a record set.

Read

zone *

-

dns:recordset:update

Grants permission to update a record set.

Write

zone *

-

-

dns:recordset:delete

Grants permission to delete a record set.

Write

zone *

-

-

dns:zone:setStatus

Grants permission to set the zone status.

Write

zone *

-

dns:recordset:setStatus

Grants permission to set the record set status.

Write

zone *

-

-

dns:recordset:associatehealthcheck

Grants permission to associate a record set with a health check.

Write

zone *

-

-

dns:recordset:disassociatehealthcheck

Grants permission to disassociate a record set from a health check.

Write

zone *

-

-

dns:ptr:list

Grants permission to list the PTR records.

List

ptr *

-

-

-

dns:ptr:get

Grants permission to obtain a PTR record.

Read

ptr *

-

dns:ptr:create

Grants permission to create a PTR record.

Write

ptr *

-

dns:ptr:set

-

dns:ptr:update

Grants permission to update a PTR record.

Write

ptr *

dns:ptr:set

dns:ptr:delete

Grants permission to delete a PTR record.

Write

ptr *

dns:ptr:set

dns:tag:get

Grants permission to query tags of a resource.

Read

zone

-

-

ptr

-

dns:tag:set

Grants permission to one or more tags to a resource.

Tagging

zone

g:ResourceTag/<tag-key>

-

ptr

g:ResourceTag/<tag-key>

dns:zone:createRetrieval

Grants permission to retrieve a zone.

Write

-

-

-

dns:zone:getRetrieval

Grants permission to query the zone retrieval status.

Read

-

-

-

dns:customLine:create

Grants permission to create a custom line.

Write

customLine *

-

-

dns:customLine:list

Grants permission to list the custom lines.

List

customLine *

-

-

dns:customLine:delete

Grants permission to delete a custom line.

Write

customLine *

-

-

dns:customLine:update

Grants permission to update a custom line.

Write

customLine *

-

-

dns:nameserver:list

Grants permission to list the name servers.

List

-

-

dns:zone:get

dns:nameserver:getZoneNameServer

Grants permission to query public DNS servers.

Read

-

-

-

dns:quota:list

Grants permission to list quotas.

List

-

-

dns:zone:get

dns:recordset:getPrivateRecordSetImport

Grants permission to query the import task record sets added to a private zone.

Read

zone *

dns:privateRecordset:getImport

dns:recordset:getPrivateRecordSetImportTemplate

Grants permission to download the template for importing record sets added to a private zone.

Read

-

-

dns:privateRecordset:getImport

dns:recordset:createPrivateRecordSetImport

Grants permission to create an import task for record sets added to a private zone.

Write

zone *

dns:privateRecordset:createImport

dns:recordset:deletePrivateRecordSetImportTask

Grants permission to delete the import task record sets added to a private zone.

Write

zone *

dns:privateRecordset:deleteImport

dns:recordset:createPublicRecordSetImport

Grants permission to create an import task for record sets added to a public zone.

Write

zone *

dns:publicRecordset:createImport

dns:recordset:getPublicRecordSetImport

Grants permission to query the import task for record sets added to a public zone.

Read

zone *

dns:publicRecordset:getImport

dns:recordset:getPublicRecordSetImportTemplate

Grants permission to download the template for importing record sets added to a public zone.

Read

-

-

dns:publicRecordset:getImport

dns:recordset:deletePublicRecordSetImportTask

Grants permission to delete the import task for record sets added to a public zone.

Write

zone *

dns:publicRecordset:deleteImport

dns:zone:getExport

Grants permission to export zones.

Read

zone *

-

dns:lineGroup:create

Grants permission to create a line group.

Write

lineGroup *

-

-

dns:lineGroup:list

Grants permission to list the line groups.

List

lineGroup *

-

-

dns:lineGroup:get

Grants permission to query a line group.

Read

lineGroup *

-

-

dns:lineGroup:delete

Grants permission to delete a line group.

Write

lineGroup *

-

-

dns:lineGroup:update

Grants permission to update a line group.

Write

lineGroup *

-

-

dns:endpoint:create

Grants permission to create a resolver endpoint.

Write

endpoint *

-

-

dns:endpoint:list

Grants permission to list the resolver endpoints.

List

endpoint *

-

-

dns:endpoint:get

Grants permission to query a specified resolver endpoint.

Read

endpoint *

-

-

dns:endpoint:update

Grants permission to update a resolver endpoint.

Write

endpoint *

-

-

dns:endpoint:delete

Grants permission to delete a resolver endpoint.

Write

endpoint *

-

-

dns:endpoint:createIpaddress

Grants permission to bind a specified IP address with a resolver endpoint.

Write

endpoint *

-

-

dns:endpoint:deleteIpaddress

Grants permission to unbind a specified IP address from a resolver endpoint.

Write

endpoint *

-

-

dns:endpoint:listIpaddresses

Grants permission to list the IP addresses bound to a resolver endpoint.

List

endpoint *

-

-

dns:endpoint:listVpcs

Grants permission to list the VPCs associated with a resolver endpoint.

List

endpoint *

-

-

dns:resolverRule:create

Grants permission to create a resolver rule to route queries originating from your VPC out of the VPC.

Write

resolverRule *

-

-

dns:resolverRule:list

Grants permission to list the resolver rules.

List

resolverRule *

-

-

dns:resolverRule:get

Grants permission to query a resolver rule.

Read

resolverRule *

-

-

dns:resolverRule:update

Grants permission to update a resolver rule.

Write

resolverRule *

-

-

dns:resolverRule:delete

Grants permission to delete a resolver rule.

Write

resolverRule *

-

-

dns:resolverRule:associaterouter

Grants permission to associate a resolver rule with a VPC.

Write

resolverRule *

-

-

dns:resolverRule:disassociaterouter

Grants permission to disassociate a resolver rule from a VPC.

Write

resolverRule *

-

-

dns:zone:enableDnssecConfig

Grants permission to enable the DNSSEC configuration for a public zone.

Write

zone *

-

dns:zone:disableDnssecConfig

Grants permission to disable the DNSSEC configuration for a public zone.

Write

zone *

-

dns:zone:getDnssecConfig

Grants permission to query the DNSSEC configuration from a public zone.

Read

zone *

-

dns:zone:listPublicZoneBatchOperationRecords

Grants permission to list batch operations of public zones.

List

-

-

dns:recordset:get

dns:zone:getPublicZoneBatchOperationResult

Grants permission to download the public zones that failed to be operated in a batch operation.

Read

-

-

dns:recordset:get

dns:recordset:batchImportPublicRecordSet

Grants permission to import record sets added to public zones.

Write

-

-

-

dns:zone:createAuthorizeTxtRecord

Grants permission to authorize a zone.

Write

-

-

-

dns:zone:getAuthorizeTxtRecord

Grants permission to query the zone authorization status.

Read

-

-

-

dns:zone:getDomainDetection

Grants permission to query the detection result of a public zone record set.

Read

zone *

-

Each API of DNS usually supports one or more actions. Table 2 lists the supported actions and dependencies.

Table 2 Actions and dependencies supported by DNS APIs

API

Action

Dependencies

GET 01 /v2/zones

dns:zone:list

-

POST 05 /v2/zones

dns:zone:create

  • dns:tag:set
  • dns:quota:list

GET 01 /v2/zones/{zone_id}

dns:zone:get

-

PATCH 03 /v2/zones/{zone_id}

dns:zone:update

-

DELETE 02 /v2/zones/{zone_id}

dns:zone:delete

  • ces:siteMonitorRule:showHealthCheck
  • ces:siteMonitorRule:put
  • ces:siteMonitorRule:delete
  • ces:siteMonitorRule:list

GET 01 /v2/zones/{zone_id}/nameservers

dns:zone:get

-

GET /v2/zones

dns:zone:list

-

POST 02 /v2/zones

dns:zone:create

  • vpc:vpcs:get
  • dns:tag:set
  • dns:quota:list

GET 04 /v2/zones/{zone_id}

dns:zone:get

-

PATCH 06 /v2/zones/{zone_id}

dns:zone:update

-

DELETE 05 /v2/zones/{zone_id}

dns:zone:delete

-

GET /v2/zones/{zone_id}/nameservers

dns:zone:get

-

POST /v2/zones/{zone_id}/associaterouter

dns:zone:associaterouter

vpc:vpcs:get

POST /v2/zones/{zone_id}/disassociaterouter

dns:zone:disassociaterouter

vpc:vpcs:get

GET /v2/zones/{zone_id}/recordsets

dns:recordset:list

-

POST /v2/zones/{zone_id}/recordsets

dns:recordset:create

  • dns:recordset:associatehealthcheck
  • ces:siteMonitorRule:showHealthCheck
  • ces:siteMonitorRule:put
  • ces:siteMonitorRule:delete
  • ces:siteMonitorRule:list
  • dns:quota:list

GET /v2/zones/{zone_id}/recordsets/{recordset_id}

dns:recordset:get

-

PUT 02 /v2/zones/{zone_id}/recordsets/{recordset_id}

dns:recordset:update

-

DELETE 01 /v2/zones/{zone_id}/recordsets/{recordset_id}

dns:recordset:delete

  • dns:recordset:disassociatehealthcheck
  • ces:siteMonitorRule:showHealthCheck
  • ces:siteMonitorRule:put
  • ces:siteMonitorRule:delete
  • ces:siteMonitorRule:list

GET /v2/recordsets

dns:recordset:list

-

PUT /v2/zones/{zone_id}/statuses

dns:zone:setStatus

-

GET /v2.1/recordsets

dns:recordset:list

-

POST /v2.1/zones/{zone_id}/recordsets

dns:recordset:create

  • dns:recordset:associatehealthcheck
  • ces:siteMonitorRule:showHealthCheck
  • ces:siteMonitorRule:put
  • ces:siteMonitorRule:delete
  • ces:siteMonitorRule:list
  • dns:quota:list

GET 03 /v2.1/zones/{zone_id}/recordsets

dns:recordset:list

-

GET 01 /v2.1/zones/{zone_id}/recordsets/{recordset_id}

dns:recordset:get

-

PUT 03 /v2.1/zones/{zone_id}/recordsets/{recordset_id}

dns:recordset:update

-

DELETE 02 /v2.1/zones/{zone_id}/recordsets/{recordset_id}

dns:recordset:delete

  • dns:recordset:disassociatehealthcheck
  • ces:siteMonitorRule:showHealthCheck
  • ces:siteMonitorRule:put
  • ces:siteMonitorRule:delete
  • ces:siteMonitorRule:list

PUT /v2.1/recordsets/{recordset_id}/statuses/set

dns:recordset:setStatus

-

POST /v2.1/zones/{zone_id}/recordsets/batch/lines

dns:recordset:create

  • dns:recordset:associatehealthcheck
  • ces:siteMonitorRule:showHealthCheck
  • ces:siteMonitorRule:put
  • ces:siteMonitorRule:delete
  • ces:siteMonitorRule:list
  • dns:quota:list

PUT /v2.1/zones/{zone_id}/recordsets

dns:recordset:update

-

DELETE /v2.1/zones/{zone_id}/recordsets

dns:recordset:delete

  • dns:recordset:disassociatehealthcheck
  • ces:siteMonitorRule:showHealthCheck
  • ces:siteMonitorRule:put
  • ces:siteMonitorRule:delete
  • ces:siteMonitorRule:list

GET /v2/reverse/floatingips

dns:ptr:list

-

GET 02 /v2/reverse/floatingips/{region}:{floatingip_id}

dns:ptr:get

-

PATCH 01 /v2/reverse/floatingips/{region}:{floatingip_id}

dns:ptr:create

  • eip:publicIps:get
  • dns:tag:set
  • dns:quota:list

PATCH 04 /v2/reverse/floatingips/{region}:{floatingip_id}

dns:ptr:update

-

PATCH 03 /v2/reverse/floatingips/{region}:{floatingip_id}

dns:ptr:delete

-

GET /v2/{project_id}/{resource_type}/tags

dns:tag:get

-

GET 02 /v2/{project_id}/{resource_type}/{resource_id}/tags

dns:tag:get

-

POST /v2/{project_id}/{resource_type}/{resource_id}/tags

dns:tag:set

-

DELETE /v2/{project_id}/{resource_type}/{resource_id}/tags/{key}

dns:tag:set

-

POST /v2/{project_id}/{resource_type}/{resource_id}/tags/action

dns:tag:set

-

POST /v2/{project_id}/{resource_type}/resource_instances/action

dns:tag:get

-

POST /v2.1/customlines

dns:customLine:create

dns:quota:list

GET /v2.1/customlines

dns:customLine:list

-

DELETE /v2.1/customlines/{line_id}

dns:customLine:delete

-

PUT /v2.1/customlines/{line_id}

dns:customLine:update

-

GET /v2/nameservers

dns:nameserver:list

-

GET /v2/quotamg/dns/quotas

dns:quota:list

-

POST /v2.1/linegroups

dns:lineGroup:create

dns:quota:list

GET /v2.1/linegroups

dns:lineGroup:list

-

GET /v2.1/linegroups/{linegroup_id}

dns:lineGroup:get

-

PUT /v2.1/linegroups/{linegroup_id}

dns:lineGroup:update

-

DELETE /v2.1/linegroups/{linegroup_id}

dns:lineGroup:delete

-

Resources

A resource type indicates the resources that an identity policy applies to. If you specify a resource type for any action in Table 3, the resource URN must be specified in the identity policy statements using that action, and the identity policy applies only to resources of this type. If no resource type is specified, the Resource element is marked with an asterisk (*) and the identity policy applies to all resources. You can also set condition keys in an identity policy to define resource types.

The following table lists the resource types that you can define in identity policy statements for DNS.

Table 3 Resource types supported by DNS

Resource Type

URN

resolverRule

dns:<region>:<account-id>:resolverRule:<resolver-rule-id>

lineGroup

dns::<account-id>:lineGroup:<line-group-id>

customLine

dns::<account-id>:customLine:<custom-line-id>

zone

dns::<account-id>:zone:<zone-id>

endpoint

dns:<region>:<account-id>:endpoint:<endpoint-id>

ptr

dns:<region>:<account-id>:ptr:<ptr-id>

Conditions

Condition Key Overview

A Condition element lets you specify conditions for when an identity policy is in effect. It contains condition keys and operators.

  • The condition key that you specify can be a global condition key or a service-specific condition key.
    • Global condition keys (with the g: prefix) apply to all actions. Cloud services do not need to provide user identity information. Instead, the system automatically obtains such information and authenticates users. For details, see Global Condition Keys.
    • Service-specific condition keys (with the abbreviation of a service name plus a colon as the prefix, for example, dns) apply only to operations of the xx service. For details, see Table 4.
    • The number of values associated with a condition key in the request context of an API call makes the condition key single-valued or multivalued. Single-valued condition keys have at most one value in the request context of an API call. Multivalued condition keys can have multiple values in the request context of an API call. For example, a request can originate from at most one VPC endpoint, so g:SourceVpce is a single-valued condition key. You can tag resources and include multiple tag key-value pairs in a request, so g:TagKeys is a multivalued condition key.
  • A condition operator, condition key, and a condition value together constitute a complete condition statement. An identity policy can be applied only when its request conditions are met. For supported condition operators, see operators.

Service-specific condition keys supported by DNS

The following table lists the condition keys that you can define in identity policies for DNS. You can include these condition keys to specify conditions for when your identity policy is in effect.

Table 4 Service-specific condition keys supported by DNS

Service-specific Condition Key

Type

Single-valued/Multivalued

Description

dns:RecordSetNames

string

Multivalued

Filters access by record set name. The name can contain only lowercase letters and cannot have the trailing dot.

dns:RecordSetTypes

string

Multivalued

Filters access by record set type. The type can be A, AAAA, MX, CNAME, TXT, NS, SRV or CAA.