tencent cloud

Tencent Cloud EdgeOne

Release Notes and Announcements
Release Notes
Security Announcement
Announcements
Product Introduction
Overview
Strengths
Use Cases
Comparison Between EdgeOne and CDN Products
Use Limits
Purchase Guide
Description of Trial Plan Experience Benefits
Free Plan Guide
Billing Overview
Billing Items
Subscriptions
Renewals
Instructions for overdue and refunds
Comparison of EdgeOne Plans
About "clean traffic" billing instructions
DDoS Protection Capacity Description
Getting Started
Choose business scenario
Quick access to website security acceleration
Quick deploying a website with Pages
Domain Service&Origin Configuration
Domain Service
HTTPS Certificate
Origin Configuration
Site Acceleration
Overview
Access Control
Smart Acceleration
Cache Configuration
File Optimization
Network Optimization
URL Rewrite
Modifying Header
Modify the response content
Rule Engine
Image&Video Processing
Speed limit for single connection download
DDoS & Web Protection
Overview
DDoS Protection
Web Protection
Bot Management
API Discovery(Beta)
Edge Functions
Overview
Getting Started
Operation Guide
Runtime APIs
Sample Functions
Best Practices
Pages
L4 Proxy
Overview
Creating an L4 Proxy Instance
Modifying an L4 Proxy Instance
Disabling or Deleting an L4 Proxy Instance
Batch Configuring Forwarding Rules
Obtaining Real Client IPs
Data Analysis&Log Service
Log Service
Data Analysis
Alarm Service
Site and Billing Management
Billing Management
Site Management
Version Management
General Policy
General Reference
Configuration Syntax
Request and Response Actions
Country/region and Corresponding Codes
Terraform
Overview
Installing and Configuring Terraform
Practical Tutorial
EdgeOne Skill User Guide
Automatic Warm-up/Cache Purge
Resource Abuse/hotlinking Protection Practical
HTTPS Related Practices
Acceleration Optimization
Scheduling Traffic
Data Analysis and Alerting
Log Platform Integration Practices
Configuring Origin Servers for Cloud Object Storage (Such As COS)
CORS Response Configuration
API Documentation
History
Introduction
API Category
Making API Requests
Site APIs
Acceleration Domain Management APIs
Site Acceleration Configuration APIs
Edge Function APIs
Alias Domain APIs
Security Configuration APIs
Layer 4 Application Proxy APIs
Content Management APIs
Data Analysis APIs
Log Service APIs
Billing APIs
Certificate APIs
Origin Protection APIs
Load Balancing APIs
Diagnostic Tool APIs
Custom Response Page APIs
API Security APIs
DNS Record APIs
Content Identifier APIs
Legacy APIs
Ownership APIs
Image and Video Processing APIs
Multi-Channel Security Gateway APIs
Version Management APIs
Data Types
Error Codes
FAQs
Product Features FAQs
DNS Record FAQs
Domain Configuration FAQs
Site Acceleration FAQs
Data and Log FAQs
Security Protection-related Queries
Origin Configuration FAQs
Troubleshooting
Reference for Abnormal Status Codes
Troubleshooting Guide for EdgeOne 4XX/5XX Status Codes
520/524 Status Code Troubleshooting Guide
521/522 Status Code Troubleshooting Guide
Tool Guide
Agreements
Service Level Agreement
Origin Protection Enablement Conditions of Use
TEO Policy
Privacy Policy
Data Processing And Security Agreement
Contact Us
Glossary

Domain Configuration FAQs

PDF
Focus Mode
Font Size
Last updated: 2025-09-02 16:33:11

Which ports are supported by default for acceleration domain access

Tencent Cloud EdgeOne (EdgeOne) default supported access ports are 80, 8080, and 443. Origin server access port configuration is unlimited, just support by the origin server.

How long does domain configuration take effect

Domain configuration usually takes effect within 5 minutes after issuance. Partial configuration may take 5-15 minutes to take effect due to a considerable number of configuration tasks. Please wait patiently.

Why does the domain still display "Please add CNAME" after being configured

Possible reasons include:
The CNAME resolution of the domain name has not taken effect. Due to the local ISP's cache, CNAME typically takes at least 5-30 minutes to take effect. Just wait patiently for the CNAME to take effect. If you have switched the NS server, the corresponding effective time may take 24-48 hr.
If your current resolution record is configured with regional resolution and only assigns DNS records for a specific region to point to the CNAME address allocated by EdgeOne, it may be because EdgeOne has no detection service in this region, which will lead to the inability to detect the corresponding domain name CNAME value, displaying "Please add CNAME". In such cases, as long as you ensure the parsing configuration is correct, the acceleration service can still be provided normally after the resolution takes effect, and the status identifier on the console can be ignored.
If you use CNAME Flattening with your domain resolution manufacturer, the DNS server will directly respond with an A record during parsing, and the CNAME record cannot be detected. In such cases, as long as you ensure the parsing configuration is correct, the acceleration service can still be provided normally after the resolution takes effect, and the status identifier on the console can be ignored.

Why does the domain name status display "CNAME configuration error" and what should be done

When the domain name status on the console displays "CNAME configuration error," it is because EdgeOne has detected that the CNAME record configured for your current domain does not point to the CNAME address assigned by EO, but instead points to a CNAME address allocated to another domain. An abnormal CNAME configuration may affect the SCDN service of the current domain if the other domain encounters issues such as deactivation or blocking. Therefore, it is recommended to Modify CNAME Resolution and change the CNAME of the current domain to the address assigned by EdgeOne.
Note:
If you first add a wildcard domain and configure a CNAME for it, and then add a subdomain included in the wildcard domain, the subdomain's CNAME status will also be detected as "CNAME configuration exception" because the system detects that the subdomain's CNAME address is the same as the wildcard domain's CNAME address. It's recommended to configure the CNAME assigned to the current subdomain to avoid service anomalies.

Help and Support

Was this page helpful?

Help us improve! Rate your documentation experience in 5 mins.

Feedback