Overview
Scenarios
Tags identify DNS resources such as public zones, private zones, and record sets. You can add tags to resources to facilitate resource identification and management.
You can add up to 20 tags to a cluster during resource creation or add them on the details page of a created resource.

If your organization has configured tag policies for the DNS service, you need to add tags to your public zones based on the tag policies. If you add a tag that does not comply with the tag policies, public zones may fail to be created. Contact the administrator to learn more about tag policies.
Basics of Tags
Tags help you identify your cloud resources. When you have many cloud resources of the same type, you can use tags to classify them by dimension (for example, use, owner, or environment).
Figure 1 shows how tags work. In this example, you assign two tags to each cloud resource. Each tag contains a key and a value that you define. The key of one tag is Owner, and the key of another tag is Usage. Each tag has a value.
You can quickly search for and filter specific cloud resources based on the tags added to them. For example, you can define a set of tags for cloud resources in an account to track the owner and usage of each cloud resource, making resource management easier.
Tag key and value requirements
- Each tag consists of a key-value pair.
- Each cloud resource can have up to 20 tags.
- For each resource, a tag key must be unique and can have only one tag value.
Parameter |
Requirements |
Example |
---|---|---|
Key |
|
example_key1 |
Value |
|
example_value1 |
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
For any further questions, feel free to contact us through the chatbot.
Chatbot