Edge Acceleration
  • Site Acceleration
    • Overview
    • Access Control
      • Token authentication
        • Token Authentication
        • Authentication Method A
        • Authentication Method B
        • Authentication Method C
        • Authentication Method D
        • Authentication Method V
    • Smart Acceleration
    • Cache configuration
      • Overview
      • EdgeOne caching rules introduction
        • Content Cache Rules
        • Cache Key Introduction
        • Vary Feature
      • Cache Configuration
        • Custom Cache Key
        • Node Cache TTL
        • Status Code Cache TTL
        • Browser Cache TTL
        • Offline Caching
        • Cache Prefresh
      • Clear and Preheat Cach
        • Cache Purge
        • URL Pre-Warming
        • Prefetch M3U8
      • How to improve the Cache Hit Rate of EdgeOne
    • File Optimization
      • Content Compression
      • Smart Compression
    • Network Optimization
      • HTTP/2
      • HTTP/3(QUIC)
        • Overview
        • Enable HTTP/3
        • QUIC SDK
          • SDK Overview
          • SDK Download and Integration
          • Sample Code
            • Android
            • iOS
          • API Documentation
            • Android
            • iOS
      • IPv6 Access
      • Maximum Upload Size
      • WebSocket
      • Client IP Geolocation Header
      • Client IP Geographical Location
      • gRPC
      • Network Error Logging
    • URL Rewrite
      • Access URL Redirection
      • Origin-Pull URL Rewrite
    • Modifying Header
      • Modifying HTTP Response Headers
      • Modifying HTTP Request Headers
    • Modify response content
      • HTTP Response
      • Custom Error Page
    • Rules Engine
      • Overview
      • Rule Management
      • variables
      • Supported Matching Types and Actions
    • Image and video processing
      • Audio and Video Pre-pulling
      • Just-in-Time Image Processing
      • Video Just-In-Time Processing
      • VOD Media Origin
    • Speed limit for single connection download
    • Request and Response Actions
      • HTTP Response
      • Processing order
      • Default HTTP Headers of Origin-Pull Requests
      • Default HTTP Response Headers
      • HTTP Restrictions
    • Media Services
      • Audio and Video Pre-pulling
      • Just-in-Time Image Processing
      • Just-in-Time Media Processing
      • VOD Media Origin
  • 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
      • Obtaining Real TCP Client IPs via TOA
      • Obtaining Real Client IPs Through Protocol V1/V2
        • Overview
        • Method 1: Obtaining Real Client IPs Through Nginx
        • Method 2: Parsing Real Client IPs on Application Server
        • Format of Real Client IPs Obtained Through Proxy Protocol V1/V2
      • Transmitting Client Real IP via SPP Protocol
  • Domain name service and origin server configuration
    • Domain Name Services
      • Overview
      • DNS resolution for managed domains
        • Modifying DNS Servers
        • Configuring DNS Records
        • Batch Importing DNS Records
        • Advanced DNS Configuration
      • Access accelerated domains
        • Adding A Domain Name for Acceleration
        • Ownership Verification
        • Modifying CNAME Records
        • Verify Business Access
      • Traffic scheduling
        • Traffic Scheduling Management
    • HTTPS Certificate
      • Overview
      • Edge HTTPS Certificate
        • Overview
        • Deploying/Updating SSL Certificate for A Domain Name
        • Configuring A Free Certificate for A Domain Name
        • Using Keyless Certificate
      • Edge mTLS Authentication
      • Origin Certificate Validation
      • HTTPS configuration
        • Forced HTTPS Access
        • Enabling HSTS
        • SSL/TLS security configuration
          • Configuring SSL/TLS Security
          • TLS Versions and Cipher Suites
        • Enabling OCSP Stapling
      • Related References
        • Using OpenSSL to Generate Self-Signed Certificates
        • Certificate Format Requirements
        • The Difference Between one-way authentication and Mutual authentication
    • Origin Configuration
      • Load Balancing
        • Overview
        • Quickly Create Load Balancers
        • Health Check Policies
        • Viewing the Health Status of Origin Server
        • Related References
          • Load Balancing-Related Concepts
          • Introduction to Request Retry Strategy
      • Origin Group Configuration
      • Origin configuration
        • Origin-Pull Timeout
        • Configuring Origin-Pull HTTPS
        • Host Header Rewrite
        • Controlling Origin-pull Requests
        • Redirect Following During Origin-Pull
        • HTTP/2 Origin-Pull
        • Range GETs
        • Modify Origin
        • Origin-pull Rate Limiting Policy
      • Origin Protection(Obtaining/Updating Origin IP Address Range)
      • Related References
        • ld Version Origin Group Compatible Related Issues
Docs Overview/
Edge Acceleration/
Domain name service and origin server configuration/
Domain Name Services/
Access accelerated domains/
Modifying CNAME Records/

Modifying CNAME Records

After a domain name is created, EdgeOne will assign a CNAME address to it. You need to complete the CNAME configuration to enable secure acceleration for the domain name.

Scenario 1: One-click CNAME Addition in NS Mode or DNSPod Managed Mode

In DNSPod managed access mode, domain names support one-click CNAME addition, helping you quickly complete the CNAME configuration.
1. Log in to the Tencent Cloud EdgeOne console, enter Service Overview in the left menu bar, and click the site to be configured under Website Security Acceleration.
2. On the left navigation bar, click Domain Name Service > Domain Management to enter the domain name management page.
3. If the current domain name has not yet configured with a CNAME, click One-click Add in the status column.

4. In the pop-up window, after confirming the relevant CNAME information that EdgeOne will operate on, click OK . In the second pop-up window, click OK again to make EdgeOne automatically complete the CNAME configuration for you.

Scenario 2: Manual CNAME Configuration

1. After a domain is added, EdgeOne provides you a CNAME pointed to the EdgeOne node.

2. Go to the DNS service provider of the domain name and add a CNAME record. See below for examples for different DNS service providers.
Tencent Cloud DNSPod
Alibaba Cloud DNS
Godaddy
a. Log in to the DNSPod console. Find the domain to verify in My Domains. Click the domain to enter the domain name configuration page.



b. On the domain name configuration page, click Add Record to add a DNS record for the domain name.


c. Enter the record type, host record, and record value obtained in Step 1.


Parameter name
Description
Record type
CNAME
Host
Enter the domain name
ISP Line
Default
Domain
Enter the CNAME provided by EdgeOne.
TTL
600
d. Click OK.
a. Log in to the Alibaba Cloud DNS console.
b. On the Manage DNS page, find the target domain name, and click Configure in the Actions column to go to the DNS Settings page.
c. Click Add Record to add a CNAME record for the domain name.
d. Enter the record type, host record, and record value obtained in Step 1.
Parameter name
Description
Record type
CNAME
Host
Enter the domain name
ISP Line
Default
Record value
Enter the CNAME provided by EdgeOne.
TTL
10 minute
e. Click OK.
b. On the Portfolio page, click the target domain name to go to the Domain Settings page.

c. Click Add to add a DNS record for ownership verification of the domain name.

d. Enter the record type, host record, and record value obtained in Step 1.

Parameter name
Description
Type
CNAME
Name
Enter the domain name
Value
Enter the CNAME provided by EdgeOne.
TTL
Default
e. Click Add Record.
3. Now, the Status of the domain should be Validated.



Verifying CNAME Records

After you complete the CNAME configuration, EdgeOne automatically detects whether the CNAME configuration has taken effect. In the domain list, if the Status column of the accelerated domain is Activated, the domain is correctly configured and accelerated.



If you have correctly configured the CNAME record, but the status is CNAME unconfigured, this may be caused by the CNAME resolution latency of the DNS provider. In this case, you can manually verify the connection by using the following methods:
Windows
Mac/Linux
Open the command prompt and run the nslookup -qt=cname www.example.com command. Then, check the CNAME information of the domain. If the CNAME information is the same as that provided by EdgeOne, DNS of the accelerated domain has been switched to EdgeOne.


Open the terminal and run the dig www.example.com command. Then, check the CNAME information of the domain. If the CNAME information is the same as that provided by EdgeOne, DNS of the accelerated domain has been switched to EdgeOne.