Edge Acceleration
  • Site Acceleration
    • Overview
    • Quickly Import and Export Site Configuration
    • Access Control
      • Token Authentication
    • Smart Acceleration
    • 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
    • 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
  • 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
      • 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
      • 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
      • Related References
        • ld Version Origin Group Compatible Related Issues
      • 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
このページは現在英語版のみで提供されており、日本語版も近日中に提供される予定です。ご利用いただきありがとうございます。

Ownership Verification

Applicable Scenarios

When your site/domain name is connected to EdgeOne for the first time, in order to ensure that you are the owner of the currently accessed site/domain name, we need you to verify the ownership of the site/domain name.
Note:
This operation is only required in CNAME connection. If your site is accessed in NS mode, you can directly switch the DNS server to EdgeOne to complete the ownership verification.

Differences Between Domain and Site Verification

Assume that you have domain names a.example.com, b.example.com, c.example.com and the site you connected is example.com.
Siteverification: If you have permission to configure DNS root domain resolution or root name server, use this method to reduceoperating costs.
Once yourownership of the site is verified by EdgeOne, you can directly add itssubdomain names a.example.com, b.example.com, c.example.com.
Domainverification: If your company is a multi-levelbusiness or provides domain operations and maintenance and you only havepermission to configure DNS resolution and the origin server for the subdomainnames, you can skip verification when connecting the site. However, all itssubdomain names need to be verified before being added.
Using domainverification requires you to verify a.example.com, b.example.com and c.example.com before connection.
Once yourownership of these domain names is verified, you can directly add all theirsubdomain names. For instance, when a.example.com is verified, test.a.example.com can be directly added.

Steps to Verify the Site or Domain Name Ownership

The verification steps of site ownership are the same as those of domain name ownership. The following example describes how to verify the site ownership.
DNS Verification
File Verification
1. On the Verify your site page, select DNS verification to obtain the host record, record type, and record value required for ownership verification.

2. Log in to the console of the DNS service provider of the domain name and add a TXT record for the verification of the site ownership. The following examples describe how to add the TXT record in the console of different DNS service providers.
Tencent Cloud DNSPod
Alibaba Cloud DNS
Godaddy
a. Log in to the DNSPod console and click My Domains in the left sidebar. On the page that appears, click the target domain name to enter its configuration page.

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

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

Parameter
Description
Record Type
TXT
Host
edgeonereclaim
Split Zone
Default
Text content
Enter the record value 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 DNS record for ownership verification of the domain name.

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

Parameter
Description
Type
TXT
Host
edgeonereclaim
ISP Line
Default
Value
Enter the record value provided by EdgeOne
TTL
10 minutes
d. Click OK.
a. Log in to the Godaddy Domain Portfolio console.
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
Description
Type
TXT
Name
edgeonereclaim
Value
Enter the record value provided by EdgeOne
TTL
Default
d. Click Add Record.
3. Verify whether the current TXT record is effective by the following methods:
Windows
Mac/Linux
Open the command prompt and run the nslookup -qt=txt edgeonereclaim.example.com command. Then, check the TXT record information of the domain. If the TXT record is the same as that provided by Step 1, the TXT record is effective.

Open the terminal and run the dig txt edgeonereclaim.example.com command. Then, check the TXT record information of the domain. If the TXT record is the same as that provided by Step 1, the TXT record is effective.

4. After the TXT record takes effect, click Verify.
1. On the Verify your site page, select File verification.

2. The following examples describe how to perform file verification on Windows and Linux.
Windows
Linux
1. Go to the root directory of the server and create the verification directory .well-known/teo-verification.
2. Click the file URL in Step 2 to get the verification file and upload it to the verification directory.

3. Copy the URL in Step 3 to your browser and make sure that the resource is accessible.
4. Click Verify.
1. Open a command window and get to the web server's root directory.
2. Copy the code in Step 2 to the command window and run it.



3. Copy the URL in Step 3 to your browser and make sure that the resource is accessible.
4. Click Verify.