Esta página aún no está disponible en su idioma local. Estamos trabajando arduamente para agregar más versiones de idiomas. Gracias por tu apoyo.
- What's New
- Function Overview
- Service Overview
- Getting Started
-
User Guide
- Public Zones
- Private Zones
- Record Sets
- PTR Records
- Intelligent Resolution
- Permissions Management
- Using CTS to Collect DNS Key Operations
- Quota Adjustment
- Change History
-
API Reference
- Before You Start
- API Overview
- Calling APIs
- APIs
- Examples
- Permissions Policies and Supported Actions
- Appendix
- Best Practices
-
FAQs
-
DNS Overview
- Will I Be Billed for the DNS Service?
- How Many Zones, PTR Records, and Record Sets Can I Create?
- What Are Huawei Cloud DNS Servers?
- What Are Huawei Cloud Private DNS Server Addresses?
- What Are the Differences Between Public and Private Domain Names?
- Does DNS Support IPv6?
- Does DNS Support Explicit and Implicit URLs?
- Does DNS Support Dynamic Domain Name Resolution?
- Does DNS Support Wildcard Entries?
- What Is TTL?
- How Many Domain Name Levels Does DNS Support?
- How Are Zones Queried to Resolve a Domain Name?
- What Are the Priorities of Resolution Lines?
- Why Was the Email Address Format Changed in the SOA Record?
- What Is CAA?
- Why Should I Set Priority For an MX Record Set?
- Can DNS Point a Domain Name to a Specific Port?
- Invalid Domain Resolution
- Website Access Failures
-
Public Zones
- Why Is a Message Indicating Conflict with an Existing Record Set Displayed When I Add a Record Set?
- How Do I Add Record Sets to Subdomains?
- Which IP Address Is Returned for the Domain Name If There Are Multiple IP Addresses in a Record Set?
- Can I Modify a Zone?
- Can DNS Translate a Domain Name to IP Addresses of On-premises Servers or Third-Party Servers?
- How Can Multiple Domain Names Be Linked to the Same Website?
- How Do I View and Change the DNS Servers of a Domain Name?
-
Private Zones
- Why Is a Message Indicating Conflict with an Existing Record Set Displayed When I Add a Record Set?
- How Do I Change Default DNS Servers of an ECS to Huawei Cloud Private DNS Servers?
- How Can I Access an ECS Using Its Host Name?
- How Can I Map the Private IP Address of an ECS to a Domain Name?
- How Can I Use a Private Domain Name to Route Internet Traffic?
- Can I Use Private Domain Names Across Regions?
- Do I Need to Register Private Domain Names?
- Will a Deleted VPC Be Automatically Disassociated from the Private Zone?
- Are Private DNS Server Addresses the Same for All Users?
- What Are the Restrictions on Concurrent Private DNS Requests?
- Reverse Resolution
- Domain Transfer
-
DNS Overview
Importing Record Sets
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. This feature is available for both public and private zones.
You can import up to 500 record sets at a time.
Before importing record sets, you have created public or private zones on the DNS console. For details, see Creating a Public Zone or Creating a Private Zone.
Procedure
- Go to the DNS console.
- In the navigation pane on the left, choose Public Zones or Private Zones.
The zone list is displayed.
- (Optional) If you have selected Private Zones, click
on the upper left corner to select the region and project.
- In the zone list, click the domain name example.com (an example domain name used in this topic).
- Click Export and Import.
- Click Download template.
- Enter your record sets in the template as required.
NOTE:
Ensure that the content is imported based on the format of the template, or the import will fail.
- Click Import Record Set and select the record set file to import.
After the import is complete, you can check whether record sets are successfully imported or not.
- Successful Import: The number of successfully imported record sets are displayed.
- Failed Import: All failed record sets are listed. You can resolve the problems based on the causes.
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.