请选择
Edge Acceleration
  • Site Acceleration
    • Overview
    • Access Control
      • Token Authentication
    • File Optimization
      • 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
    • URL Rewrite
      • Access URL Redirection
      • Origin-Pull URL Rewrite
    • Modifying Header
      • Modifying HTTP Response Headers
      • Modifying HTTP Request Headers
    • Custom Error Page
    • Request and Response Actions
      • Processing order
      • Default HTTP Headers of Origin-Pull Requests
      • Default HTTP Response Headers
  • Smart Acceleration
  • 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
  • Edge DNS
    • Hosting DNS Records
      • Modifying DNS Servers
      • Configuring DNS Records
      • Advanced DNS Configuration
    • Domain Connection
      • Adding A Domain Name for Acceleration
      • Ownership Verification
      • Modifying CNAME Records
    • Domain alias
      • Overview
      • Configuration Guide
      • Batch Connecting SaaS Domain Names
      • Configuring Alias Domain Names for Disaster Recovery
    • Traffic Scheduling
      • Traffic Scheduling Management
    • 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-pull configuration
        • Configuring Origin-Pull HTTPS
        • Host Header Rewrite
        • Controlling Origin-pull Requests
        • Redirect Following During Origin-Pull
        • HTTP/2 Origin-Pull
        • Range GETs
      • Related References
        • ld Version Origin Group Compatible Related Issues
        • VOD Origin Server Details
      • Collect EdgeOne origin-pull node IP
  • Edge Cache
    • Overview
    • EdgeOne Cache Rules
      • 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
    • How to improve the Cache Hit Rate of EdgeOne
  • Rules Engine
    • Overview
    • Supported Matching Types and Actions
    • Rule Management
    • variables
  • Image Processing
Docs Overview/
Edge Acceleration/
Edge DNS/
Domain Connection/
Modifying CNAME Records/

Modifying CNAME Records

This document describes how to change the CNAME of a domain name.
Note:
This is only required for sites connected via the CNAME. You don't need to do this for sites connected via the NS.

Scenarios

In CNAME access mode, besides adding an acceleration domain name or alias domain, you also need to configure the CNAME record at your DNS service provider before you can direct user access to EdgeOne nodes and make the acceleration take effect.

Directions

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.