- What's New
- Function Overview
- Service Overview
- Getting Started
-
User Guide
- Public Zones
- Private Zones
- Record Sets
- PTR Records
- Intelligent Resolution
- Resolver
- Permissions Management
- Using CTS to Collect DNS Key Operations
- Access Logging
- Quota Adjustment
- Best Practices
-
API Reference
- Before You Start
- API Overview
- Calling APIs
- APIs
- Examples
- Permissions Policies and Supported Actions
- Appendix
- SDK Reference
-
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 Forwarding and Implicit Forwarding?
- 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 Handle the Conflict Between CNAME and MX Record Sets?
- 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?
- Configuring Weighted Routing
- Can DNS Resolve a Domain Name that Has Not Been Licensed?
- Does DNS Support Dynamic Domain Name Resolution?
- How Do I Change the DNS Servers of a Domain Name?
- How Do I Handle Inaccurate Scheduling Caused by the CNAME Record Set Cache in the Default Lines?
-
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 Queries?
- Reverse Resolution
- Domain Transfer
-
DNS Overview
- Videos
-
More Documents
-
User Guide (ME-Abu Dhabi Region)
- Overview
- Getting Started
- Private Zone
- Record Set
- PTR Record
- Permissions Management
- Key Operations Recorded by CTS
- Quota Adjustment
- FAQs
- Change History
- API Reference (ME-Abu Dhabi Region)
-
User Guide (Paris Region)
- Overview
- Getting Started
- Public Zones
- Private Zones
- Record Sets
- PTR Records
- Intelligent Resolution
- Permissions Management
- Key Operations Recorded by CTS
- Quota Adjustment
-
FAQ
-
DNS Overview
- Will I Be Billed for the DNS Service?
- How Many Zones, PTR Records, and Record Sets Can I Create?
- What Are DNS Servers?
- 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?
- 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?
-
Public Zones
- 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?
- What Can I Do If There Is Message Indicating that the Public Zone Already Exists?
- Can I Modify a Zone?
- How Can Multiple Domain Names Be Linked to the Same Website?
- Configuring Weighted Routing
-
Private Zones
- How Can I Map the Private IP Address of an ECS to a Domain Name?
- 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
-
DNS Overview
- Change History
- API Reference (Paris Region)
-
User Guide (Kuala Lumpur Region)
- Overview
- Getting Started
- Private Zone
- Record Set
- Permissions Management
- Key Operations Recorded by CTS
- Quota Adjustment
-
FAQs
-
DNS Overview
- Will I Be Billed for the DNS Service?
- How Many Zones and Record Sets Can I Create?
- What Are the Private DNS Servers Provided by the DNS Service?
- Does DNS Support Wildcard Entries?
- How Are Zones Queried to Resolve a Domain Name?
- Why Was the Email Address Format Changed in the SOA Record?
- Can DNS Point a Domain Name to a Specific Port?
- Private Zones
-
DNS Overview
- Change History
- API Reference (Kuala Lumpur Region)
- User Guide (Ankara Region)
- API Reference (Ankara Region)
-
User Guide (ME-Abu Dhabi Region)
- Glossary
- General Reference
Show all
Copied.
Configuring ISP Lines
Background
Usually, a DNS server returns the same IP address to visitors from different networks. However, in cross-network access, this would lead to high latency and poor user experience.
If you configure ISP lines when you create record sets, the DNS server returns different resolution results or IP addresses to visitors based on their carrier networks.
ISP lines can be configured only for public zones.
If a resolution line becomes faulty, you cannot switch to another resolution line.
For example, you have built a website using domain name example.com and hosted the website on three servers, with one in a China Telecom equipment room, one in a China Unicom data center, and one in a China Mobile data center. You need to configure four ISP lines: Default, China Telecom, China Unicom, and China Mobile.
ISP Lines
ISP lines are categorized by telecom carriers in China.
Level 1 |
Level 2 |
Level 3 |
---|---|---|
China Telecom, China Mobile, China Unicom, and Pengboshi |
Default region |
Default province |
North China |
Default, Beijing, Tianjin, Hebei, Shanxi, and Inner Mongolia |
|
Northeast China |
Default, Liaoning, Jilin, and Heilongjiang |
|
Northwest China |
Default, Shaanxi, Gansu, Qinghai, Ningxia, and Xinjiang |
|
Central China |
Default, Henan, Hubei, and Hunan |
|
East China |
Default, Shanghai, Jiangsu, Zhejiang, Anhui, Fujian, Jiangxi, and Shandong |
|
South China |
Default, Guangdong, Hainan, and Guangxi |
|
Southwest China |
Default, Chongqing, Sichuan, Guizhou, Yunnan, and Tibet |
|
Jiaoyuwang and Tietong |
Default |
Default province |
For example, you have configured the following resolution lines for record set example.com:
- Default: 1.1.1.1
- China Telecom: 2.2.2.2
- China Telecom_North China: 3.3.3.3
When a China Telecom user in North China requests the domain name example.com, IP address 3.3.3.3 is returned. When a China Telecom user in another region requests this domain name, IP address 2.2.2.2 is returned. When a non-China Telecom user in a region other than North China requests the domain name, IP address 1.1.1.1 is returned.
Procedure
Configure ISP lines for your public domain names hosted on the DNS service.
The following example describes how to configure the record set of the Default line to 1.1.1.1 and the record set of the China Telecom line to 2.2.2.2 for example.com.
- Go to the Public Zones page.
- On the Public Zones page, click the domain name (example.com) of the public zone.
The Record Sets tab is displayed.
- Click Add Record Set.
- Add two A record sets for example.com. Configure the parameters based on Table 2.
Table 2 Parameters for adding an A record set Parameter
Description
Line 1
Line 2
Name
Prefix of the domain name to be resolved.
For example, if the domain name is example.com, the prefix can be as follows:
- www: The domain name is www.example.com, which is usually used for a website.
- Left blank: The domain name is example.com.
To use an at sign (@) as the domain name prefix, just leave this parameter blank.
- abc: The domain name is abc.example.com, a subdomain of example.com.
- mail: The domain name is mail.example.com, which is usually used for email servers.
- *: The domain name is *.example.com, which is a wildcard domain name, indicating all subdomains of example.com.
www
www
Type
Type of the record set.
A – Map domains to IPv4 addresses
A – Map domains to IPv4 addresses
Line
Resolution line.
The DNS server will return the IP address of the specific line, depending on where the visitors come from.
- Default: returns the default resolution result irrespective of where the visitors come from.
- ISP: returns the resolution result based on visitors' carrier networks.
- Region: returns the resolution result based on visitors' geographical locations. For details, see Configuring Region Lines.
Default
ISP_China Telecom
TTL (s)
Cache duration of the record set on a local DNS server, in seconds.
The value ranges from 1 to 2147483647, and the default value is 300.
If your service address changes frequently, set TTL to a smaller value.
Learn more about TTL.
Default value: 300
Default value: 300
Value
IPv4 addresses mapped to the domain name.
Enter each IPv4 address on a separate line.
1.1.1.1
2.2.2.2
Weight
(Optional) Weight for the record set. The value ranges from 0 to 1000, and the default value is 1.
This parameter is only configurable for public zone record sets.
If a resolution line in a zone contains multiple record sets of the same type, you can set different weights to each record set. For details, see Configuring Weighted Routing.
1
1
Tag
(Optional) Identifier of the record set. Each tag contains a key and a value. You can add up to 20 tags to a record set.
For details about tag key and value requirements, see Table 3.
NOTE:
If you have configured tag policies for DNS, you need to add tags to your record sets based on the tag policies. If you add a tag that does not comply with the tag policies, record sets may fail to be created. Contact the administrator to learn more about tag policies.
example_key1
example_value1
example_key1
example_value1
Description
(Optional) Supplementary information about the record set.
The description can contain no more than 255 characters.
-
-
Table 3 Tag key and value requirements Parameter
Requirements
Example Value
Key
- Cannot be left blank.
- Must be unique for each resource.
- Can contain no more than 36 characters.
- Cannot start or end with a space nor contain special characters =*<>\,|/
example_key1
Value
- Cannot be left blank.
- Can contain no more than 43 characters.
- Cannot start or end with a space nor contain special characters =*<>\,|/
example_value1
- Click OK.
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