Configuring Region Lines
Background
Usually, a DNS server returns the same resolution result to all visitors, irrespective of where they come from. In cross-region access, this would lead to long latency and poor user experience.
If you configure region lines when you create record sets, the DNS server returns different resolution results or IP addresses to visitors based on their locations.
Region lines can be used only in public zones. You cannot specify region lines in private zones or PTR records.
For example, you have built a website using domain name example.com and hosted the website on two servers, one in Chinese mainland and the other in another region or country. You need to configure three lines: Default, Chinese Mainland, and Global.
Region Lines
Region lines are categorized by geographic areas, as shown in Table 1.
Level 1 |
Level 2 |
Level 3 |
---|---|---|
Chinese mainland |
Default |
Default |
North China |
Beijing, Tianjin, Hebei, Shanxi, and Inner Mongolia |
|
Northeast China |
Liaoning, Jilin, and Heilongjiang |
|
Northwest China |
Shaanxi, Gansu, Qinghai, Ningxia, and Xinjiang |
|
Central China |
Henan, Hubei, and Hunan |
|
East China |
Shanghai, Jiangsu, Zhejiang, Anhui, Fujian, Jiangxi, and Shandong |
|
South China |
Guangdong, Hainan, and Guangxi |
|
Southwest China |
Chongqing, Sichuan, Guizhou, Yunnan, and Tibet |
|
Global |
Default |
Default |
Asia Pacific |
Default, Taiwan (China), Hong Kong (China), Macao (China), Japan, South Korea, India, Türkiye, Indonesia, Vietnam, Singapore, Thailand, Malaysia, Bangladesh, UAE, Armenia, Azerbaijan, Bahrain, Brunei, Bhutan, Christmas Island, Georgia, Iraq, Jordan, Kyrgyzstan, Cambodia, Kuwait, Kazakhstan, Lebanon, Sri Lanka, Myanmar, Mongolia, Maldives, Nepal, Oman, Philippines, Pakistan, Palestine, Qatar, Saudi Arabia, Tajikistan, Timor-Leste, Turkmenistan, Uzbekistan, Yemen, Cyprus, Israel, American Samoa, Cook Islands, Federated States of Micronesia, Guam, Kiribati, Marshall Islands, Northern Mariana Islands, New Caledonia, Norfolk Island, Nauru, French Polynesia, Papua New Guinea, Palau, Solomon Islands, Tokelau Islands, Tonga, Tuvalu, Vanuatu, Samoa, Afghanistan, Laos, Iran, and Syria |
|
Oceania |
Default, Australia, New Zealand, Fiji Islands, Wallis and Futuna, and Niue |
|
Europe |
Default, United Kingdom, Germany, France, Italy, Russia, Spain, Ukraine, the Netherlands, Sweden, Poland, British Indian Ocean Territory, Belarus, Andorra, Albania, Austria, Aland Islands, Belgium, Bulgaria, Switzerland, Czech Republic, Denmark, Estonia, Finland, Faroe Islands, Guernsey, Gibraltar, Greece, Croatia, Hungary, Ireland, Isle of Man, Iceland, Jersey, Liechtenstein, Lithuania, Luxembourg, Latvia, Monaco, Moldova, Montenegro, North Macedonia, Malta, Norway, Portugal, Romania, Serbia, Slovenia, Slovakia, San Marino, Vatican, Kosovo, Svalbard and Jan Mayen, and Netherlands Caribbean |
|
North America |
Default, United States, Canada, Mexico, Antigua and Barbuda, Barbados, Bahamas, Belize, Costa Rica, the Commonwealth of Dominica, the Dominican Republic, Grenada, Guatemala, Honduras, Haiti, Jamaica, Saint Kitts and Nevis, Cayman Islands, Saint Lucia, Nicaragua, Panama, Puerto Rico, El Salvador, Turks and Caicos Islands, Trinidad and Tobago, British Virgin Islands, United States Virgin Islands, and Saint Vincent and the Grenadines Saint Martin, Saint Pierre and Miquelon, Cuba, Greenland, French Martinique Islands-Martinique, and Sint Maarten |
|
South America |
Default, Brazil, Argentina, Anguilla, Aruba, St. Barthelemy, Bermuda, Guadeloupe, Montserrat, Bolivia, Chile, Colombia, Curaçao, Ecuador, French Guiana, Guyana, Peru, Paraguay Uruguay, Suriname, Uruguay, and Venezuela |
|
Africa |
Default, South Africa, Egypt, Angola, Burkina Faso, Burundi, Benin, Botswana, Congo-Kinshasa, Central African Republic, the Republic of Congo, Ivory Coast, Cameroon, Cape Verde, Djibouti, Algeria, Eritrea, Ethiopia, Gabon, Ghana, Gambia, Guinea, Equatorial Guinea, Guinea-Bissau, Kenya, Comoros, Liberia, Lesotho, Libya, Morocco, Madagascar, Mali, Mauritania, Mauritius, Malawi, Mozambique, Niger, Nigeria, Reunion, Rwanda, Seychelles, Sierra Leone, Senegal, Somalia, South Sudan, Sao Tome and Principe, Eswatini, Chad, Togo, Tunisia, Tanzania, Uganda, Mayotte, Zambia, Zimbabwe, Namibia, and Sudan |
|
Antarctica |
Default, Antarctica |
Suppose you have configured the following resolution lines for example.com:
- Default: 1.1.1.1
- Chinese Mainland: 2.2.2.2
- Global_Hong Kong (China): 3.3.3.3
When a visitor in Shanghai requests the domain name example.com, IP address 2.2.2.2 is returned. When a visitor in Hong Kong requests this domain name, IP address 3.3.3.3 is returned. When a visitor in New Zealand requests this domain name, IP address 1.1.1.1 is returned.
Procedure
Configure region lines for your public domain names hosted on the DNS service.
The following describes how to configure a Default line to map the domain name to 1.1.1.1 and a Global_Hong Kong (China) line to map the domain name to 2.2.2.2.
- 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.
The Add Record Set dialog box is displayed.
- 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 each record set.
A – Map domains to IPv4 addresses
A – Map domains to IPv4 addresses
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. For details, see Configuring ISP Lines.
- Region: returns the resolution result based on visitors' geographical locations.
Default
Select Region and Global_Asia Pacific_Hong Kong (China)
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.
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.