Compute
Elastic Cloud Server
Huawei Cloud Flexus
Bare Metal Server
Auto Scaling
Image Management Service
Dedicated Host
FunctionGraph
Cloud Phone Host
Huawei Cloud EulerOS
Networking
Virtual Private Cloud
Elastic IP
Elastic Load Balance
NAT Gateway
Direct Connect
Virtual Private Network
VPC Endpoint
Cloud Connect
Enterprise Router
Enterprise Switch
Global Accelerator
Management & Governance
Cloud Eye
Identity and Access Management
Cloud Trace Service
Resource Formation Service
Tag Management Service
Log Tank Service
Config
OneAccess
Resource Access Manager
Simple Message Notification
Application Performance Management
Application Operations Management
Organizations
Optimization Advisor
IAM Identity Center
Cloud Operations Center
Resource Governance Center
Migration
Server Migration Service
Object Storage Migration Service
Cloud Data Migration
Migration Center
Cloud Ecosystem
KooGallery
Partner Center
User Support
My Account
Billing Center
Cost Center
Resource Center
Enterprise Management
Service Tickets
HUAWEI CLOUD (International) FAQs
ICP Filing
Support Plans
My Credentials
Customer Operation Capabilities
Partner Support Plans
Professional Services
Analytics
MapReduce Service
Data Lake Insight
CloudTable Service
Cloud Search Service
Data Lake Visualization
Data Ingestion Service
GaussDB(DWS)
DataArts Studio
Data Lake Factory
DataArts Lake Formation
IoT
IoT Device Access
Others
Product Pricing Details
System Permissions
Console Quick Start
Common FAQs
Instructions for Associating with a HUAWEI CLOUD Partner
Message Center
Security & Compliance
Security Technologies and Applications
Web Application Firewall
Host Security Service
Cloud Firewall
SecMaster
Anti-DDoS Service
Data Encryption Workshop
Database Security Service
Cloud Bastion Host
Data Security Center
Cloud Certificate Manager
Edge Security
Situation Awareness
Managed Threat Detection
Blockchain
Blockchain Service
Web3 Node Engine Service
Media Services
Media Processing Center
Video On Demand
Live
SparkRTC
MetaStudio
Storage
Object Storage Service
Elastic Volume Service
Cloud Backup and Recovery
Storage Disaster Recovery Service
Scalable File Service Turbo
Scalable File Service
Volume Backup Service
Cloud Server Backup Service
Data Express Service
Dedicated Distributed Storage Service
Containers
Cloud Container Engine
SoftWare Repository for Container
Application Service Mesh
Ubiquitous Cloud Native Service
Cloud Container Instance
Databases
Relational Database Service
Document Database Service
Data Admin Service
Data Replication Service
GeminiDB
GaussDB
Distributed Database Middleware
Database and Application Migration UGO
TaurusDB
Middleware
Distributed Cache Service
API Gateway
Distributed Message Service for Kafka
Distributed Message Service for RabbitMQ
Distributed Message Service for RocketMQ
Cloud Service Engine
Multi-Site High Availability Service
EventGrid
Dedicated Cloud
Dedicated Computing Cluster
Business Applications
Workspace
ROMA Connect
Message & SMS
Domain Name Service
Edge Data Center Management
Meeting
AI
Face Recognition Service
Graph Engine Service
Content Moderation
Image Recognition
Optical Character Recognition
ModelArts
ImageSearch
Conversational Bot Service
Speech Interaction Service
Huawei HiLens
Video Intelligent Analysis Service
Developer Tools
SDK Developer Guide
API Request Signing Guide
Terraform
Koo Command Line Interface
Content Delivery & Edge Computing
Content Delivery Network
Intelligent EdgeFabric
CloudPond
Intelligent EdgeCloud
Solutions
SAP Cloud
High Performance Computing
Developer Services
ServiceStage
CodeArts
CodeArts PerfTest
CodeArts Req
CodeArts Pipeline
CodeArts Build
CodeArts Deploy
CodeArts Artifact
CodeArts TestPlan
CodeArts Check
CodeArts Repo
Cloud Application Engine
MacroVerse aPaaS
KooMessage
KooPhone
KooDrive
On this page

Configuring ISP Lines

Updated on 2024-10-30 GMT+08:00

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.

NOTE:

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.

Table 1 ISP lines

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.

  1. Go to the Public Zones page.
  1. On the Public Zones page, click the domain name (example.com) of the public zone.

    The Record Sets tab is displayed.

  2. Click Add Record Set.
  1. 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

  2. Click OK.

We use cookies to improve our site and your experience. By continuing to browse our site you accept our cookie policy. Find out more

Feedback

Feedback

Feedback

0/500

Selected Content

Submit selected content with the feedback