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
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
Help Center/ Domain Name Service/ FAQs/ Public Zones/ How Do I Handle Inaccurate Scheduling Caused by the CNAME Record Set Cache in the Default Lines?

How Do I Handle Inaccurate Scheduling Caused by the CNAME Record Set Cache in the Default Lines?

Updated on 2025-02-10 GMT+08:00

Original DNS Record Sets

  1. A CNAME record set with a default line
  2. Record sets of other types (excluding CNAME), with a non-default line for each record set
Take the hwtest-example.com domain name as an example. DNS record sets are configured as follows.
Table 1 Original DNS record sets

Domain Name

Line Type

Record Set Type

Record Set Value

hwtest-example.com

Default line for China Telecom

AAAA

ff03:x:x:x:x:x:x:x

hwtest-example.com

Default line for China Telecom

A

1.x.x.x

hwtest-example.com

Default

CNAME

www.huaweicloud.com

Figure 1 DNS record sets

Cause Analysis for Inaccurate Scheduling

Table 2 Responses of different types of record sets with a non-default line

Requested Record Set Type

Record Set Type for the Line

Responses

A

  • Not found: A
  • Found: AAAA

The CNAME record set with the default line is returned and cached on the local DNS server.

CNAME record sets have the highest priority. Within the TTL, the CNAME record set with the default line is used for DNS resolution even if DNS queries to the A or AAAA record set with a non-default line are initiated. As a result, DNS scheduling is inaccurate.

  • Not found: A and AAAA
  • Found: TXT, MX, and other

AAAA

  • Not found: AAAA
  • Found: A
  • Not found: A and AAAA
  • Found: TXT, MX, and other

MX

Not found: MX

TXT

Not found: TXT

Solutions

  1. Configure A and AAAA record sets for a subdomain of the domain name, with a non-default line.
  2. Configure a CNAME record set for the domain name with a non-default line (which must be the same as the line type specified in 1) to map the domain name to the subdomain specified in the A and AAAA record sets.

Take hwtest-example.com as an example.

Configure A and AAAA record sets for www.hwtest-example.com (a subdomain of hwtest-example.com), with a China Telecom default line for each record set.

Then, configure a CNAME record set for hwtest-example.com to map it to www.hwtest-example.com.

CAUTION:
  • www.hwtest-example.com is only an example domain name. Select a second-level domain name that has no record sets configured based on your service requirements.
  • You must add A and AAAA record sets before adding a CNAME record set. If you add a CNAME record set first, DNS resolution may be interrupted.
  • The CNAME record set configured for the domain name remains unchanged.
Table 3 and Figure 2 show the optimized DNS record sets.
Table 3 Optimized DNS record sets

Domain Name

Line Type

Record Set Type

Record Set Value

hwtest-example.com

Default line for China Telecom

CNAME

www.hwtest-example.com

www.hwtest-example.com

Default line for China Telecom

AAAA

ff03:x:x:x:x:x:x:x

www.hwtest-example.com

Default line for China Telecom

A

1.x.x.x

hwtest-example.com

Default

CNAME

www.huaweicloud.com

Figure 2 Optimized DNS record sets
NOTE:

A CNAME record set with a default line and a CNAME record set with a non-default line are configured, and the two record sets have the same priority. If you request an MX or TXT record set with a non-default line and no record set of the corresponding type is configured, no response is returned. In this case, cache pollution will not occur and DNS scheduling will be accurate.

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