请选择
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
Docs Overview/
Edge Acceleration/
Edge DNS/
Hosting DNS Records/
Configuring DNS Records/

Configuring DNS Records

This document describes how to configure the DNS record on EdgeOne.
Note
This feature is only available for sites connected via the NS.

Prerequisite

1. Connect your site to EdgeOne via NS.
2. Modify the DNS server of your domain to the DNS server provided by EdgeOne. For details, see Modifying DNS Server.

Adding one DNS Record

1. Log in to the EdgeOne console. Click the target site in the site list to display second-level menus for site management.
2. In the left sidebar, click Domain Name Service > DNS Records.
3. On the DNS Record page, click Add record, complete the parameters, and click Save.

Parameter description:
Record type and Record value: Different types of records have different purposes.
Record type
Example
Description
A
8.8.8.8
Point a domain name to an IPv4 address, such as 8.8.8.8.
AAAA
2400:cb00:2049:1::a29f:f9
Point a domain name to an IPv6 address.
CNAME
cname.edgeone.com
Point a domain name to another domain name from which the final IP address is resolved.
MX
10 mail.edgeone.com
In the first box, enter the priority of mail servers to receive mails. A smaller value indicates a higher priority. In the second box, enter the mail server, which is usually provided by the mail register.
TXT
ba21a62exxxxxxxxxxcf5f06e audio/video proxy
Identify and describe a domain name. It is usually used for domain name verification and as SPF records (for anti-spam).
NS
ns01.edgeone.com audio/video proxy
If you need to have another DNS provider to resolve the sub-domain, add the NS record. Note that you cannot add an NS record for a root domain name.
SRV
1 5 7001 srvhostname.example.com
Identify a service used by a server. It is commonly used in Microsoft directory management.
CAA
0 issue "trustasia.com"
Specify CAs that are allowed to issue certificates for a site.
Host record: Prefix of the sub-domain. For example, if the site is example.com, and you want to add the domain name www.example.com, you need to enter www.
TTL: It is the DNS record cache period. A shorter TTL indicates a higher record update frequency. However the DNS resolution speed can be slightly affected.
TTL options: Default, 1 minute, 2 minutes, 5 minutes, 10 minutes, 15 minutes, 30 minutes, 1 hour, 2 hours, 200 minutes, 12 hours, and 1 day. If you select Default, the system will configure TTL to 5 seconds.
How to configure TTL:
If the record value does not change frequently, select 1 hour or longer to speed up DNS resolution.
If the record value changes frequently, select a shorter TTL value such as 1 minute, which, however, may slightly slow down DNS resolution.
Weight: Only the A/AAAA/CNAME records can be configured with a weight. The weight is empty by default, indicating no weight configuration. Its valid value range is 0-100. When the weight is set to 0, it indicates no resolution, but it is not allowed to set all weights to 0. After the weights are configured, if there are multiple resolution records with the same name, the resolution result will be returned according to the weights. The calculation method for the weight is as follows: Final effective weight = Weight of the current record/Sum of the weights of all records with the same name. The example is as follows:
Suppose that there are currently 3 CNAME records with the same host record name, namely Record A, Record B, and Record C, with the weight set to 0, 60, and 40 respectively. The final effective weight result is that Record A is not resolved, Record B's weight ratio is 60/(60 + 40) = 60%, and Record C's weight ratio is 40/(60 + 40) = 40%.
Note:
1. If the domain name you are resolving needs to be accelerated, click Enable Acceleration in the operation column. Only A/AAAA/CNAME records are supported. For common conflicts, see FAQs.
2. When you enable acceleration for a domain name, it is moved to Acceleration. You can also check it in the DNS records page.
3. If you want to configure multiple origins, or set a COS bucket as the origin, please see Adding Acceleration Domain Name.
4. Up to 15 A/AAAA/CNAME records with the same host record name can be added simultaneously.
5. If multiple A/AAAA/CNAME records have the same host record name and are configured with a weight, the weight configuration for all these records must be consistent, indicating that the weight must be configured or disabled for all these records.