Managing Record Sets in Batches
Overview
The DNS service allows you to disable, enable, export, import, and delete private zone record sets in batches.
Disabling Record Sets in Batches
You can disable record sets in the Normal status in batches.
- Go to the Private Zones page.
- Disable record sets.
- Disabling all record sets for a domain name: In the zone list, locate the target domain name and click Disable in the Operation column.
- Disabling multiple record sets: Click the target domain name to go to the record set list. Select the target record sets and click Disable above the record set list.
- Click OK.
After a record set is disabled, it cannot be used for resolution, but you can view it in the record set list.
Enabling Record Sets in Batches
You can enable record sets in the Disabled status in batches.
- Go to the Private Zones page.
- Enable record sets.
- Enabling all record sets for a domain name: In the zone list, locate the domain name and click Enable in the Operation column.
- Enabling a record set: Click the target domain name to go to the record set list. Locate the target record set, click Enable in the Operation column.
- Enabling multiple record sets: In the zone list, click the domain name to go to the record set list. Select the record sets, click Enable above the record set list.
- Click OK.
Exporting Record Sets in Batches
Scenarios
If you want to transfer your domain name to another cloud service provider, you can export all the record sets configured for the domain name in batches.
The following information can be exported: domain name, type, TTL (s), value, status, description, record set ID, time when the record set was created, and time when the record set was last modified.
Procedure
- Go to the Private Zones page.
- Click
in the upper left corner and select the desired region and project. - In the zone list, click the name of the zone whose record sets are to be exported.
- Click the Export and Import tab.
- Click Export Record Set in the upper right corner of the page.
An .xlsx file named using the domain name is exported, for example, example.com.xlsx.
In the file, you can view the following information about record sets: domain name, type, TTL (s), value, status, description, record set ID, time when the record set was created, and time when the record set was last modified.
Importing Record Sets in Batches
Scenarios
If you want to transfer your domain name from another cloud server provider to the DNS service for hosting, you can import existing record sets configured for the domain name in batches.
Constraints
- You can import a maximum of 500 record sets at a time.
- If a private zone is associated with a VPC that contains CloudDCN or CloudPond subnets, only record sets with the weight of 0 can be imported. Importing record sets with any other weight will result in resolution failures.
Before importing record sets, you have created a private zone on the DNS console. For details, see Creating a Private Zone.
- Go to the Private Zones page.
- Click
in the upper left corner and select the desired region and project. - In the zone list, click the name of the zone whose record sets are to be imported.
- Click the Export and Import tab.
- Before you import record sets, list them in the template.
- Click Download template in the note.
- Fill in the template as required.
If you have exported record sets from the previous service provider, you need to fill them in the template. If the format is incorrect, the import may fail.
- In the upper right corner of the page, click Import Record Set and select the record set file to import. You can check whether record sets are imported or not.
- Successful Import: The number of successfully imported record sets is displayed.
- Failed Import: All failed record sets are listed. You can resolve the problems based on the causes.
Before importing record sets again, click Clear in the upper right corner of the page to clear both the record sets that have been imported successfully and the record sets failed to be imported.
Deleting Record Sets in Batches
You can delete record sets in batches if they are no longer needed.
The system-generated NS and SOA record sets cannot be deleted.
Deleted record sets cannot be recovered, and domain name queries will fail. Exercise caution when performing this operation.
- Go to the Private Zones page.
- Click
in the upper left corner and select the desired region and project. - In the zone list, click the target domain name.
- In the record set list, select the record sets to be deleted.
- Click Delete above the record set list.
- In the displayed dialog box, confirm the record sets to be deleted.
Common Causes and Solutions for Batch Import Failures
| Error Message | Cause | Solution |
|---|---|---|
| There is already an import task for this domain name. Clear the existing task and then continue the import. | The record sets that failed to be batch imported were not cleared. | Click Clear in the upper right corner of the Export and Import tab and try again. |
| Invalid record set type: A, AAAA, MX, CNAME, TXT, PTR, or SRV. | The types of record sets to be imported are invalid. | Modify or delete the record sets of invalid types and try again. |
| Invalid record set value. | The values of record sets to be imported are invalid. | Modify the record set values as needed and try again. For details, see Record Set Types and Configuration Rules. |
| Invalid record set name. The record set name must be a valid domain name. | Invalid domain name configured in the record set. | Enter www for the Name field or leave it blank. You can also enter www.example.com. (a domain name with a period at the end) for the Name field. |
| Invalid zone description. The description can contain a maximum of 255 characters. | The record set description exceeds 255 characters. | Change the record set description. Value range: 0 to 255 characters. |
| Invalid TTL value. | TTL of the record sets to be imported is invalid. | Change the record set TTL. Value range: 1 to 2147483647 |
What is your overall rating for this page?
Thank 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