- Release Notes and Announcements
- Product Introduction
- Purchase Guide
- Description of 14-day Trial Plan Experience Benefits
- Billing Overview
- Basic Service Fees
- Value-added Service Fees
- Related Tencent Cloud Services
- Extra Package Description (Prepaid)
- Subscriptions
- Renewals
- Overdue and Expiration Policies
- Refund Policy
- Usage Cap Policy
- EdgeOne Plan Upgrade Guide
- Comparison of EdgeOne Plans
- Billing Usage
- About "clean traffic" billing instructions
- Getting Started
- Domain Service
- Site Acceleration
- Origin Configuration
- Edge Functions
- Overview
- Getting Started
- Operation Guide
- Runtime APIs
- Sample Functions
- Example Overview
- 301 Redirect
- Obtaining Client URL Information
- Customization Based on Client Geo Location
- Obtaining Client Geo Location Information
- Batch Redirect
- Returning an HTML Page
- Returning a JSON Object
- Fetch Remote Resources
- Authenticating a Request Header
- Modifying a Response Header
- Performing an A/B Test
- Setting Cookies
- Performing Redirect Based on the Request Location
- Using the Cache API
- Caching POST Requests
- Responding in Streaming Mode
- Merging Resources and Responding in Streaming Mode
- Protecting Data from Tampering
- Rewriting a m3u8 File and Configuring Authentication
- Adaptive Image Resize
- Image Adaptive WebP
- Customize Referer restriction rules
- Remote Authentication
- HMAC Digital Signature
- Naming a Downloaded File
- Obtaining Client IP Address
- Practical Tutorial
- Security Protection
- Overview
- DDoS Protection
- DDoS Protection Overview
- Exclusive DDoS Protection Usage
- Configuration of Exclusive DDoS protection Rules
- Web Protection
- Rules Template
- IP Groups
- Origin Protection
- Custom Response Page
- Alarm Notification
- Rule Engine
- L4 Proxy
- Data Analysis&Log Service
- Tool Guide
- Practical Tutorial
- Configuring EdgeOne Security Event Alarms via TCOP
- EdgeOne Resource Abuse Prevention
- EdgeOne Implementation of Session Persistence Based on Client IP Addresses
- EdgeOne Implementation of Origin-Pull Based on Client's Geo Location
- EdgeOne Hotlink Protection Practical Tutorial
- EdgeOne initiates Automatic Warm-up
- EdgeOne Automatic Cache Purge
- Cross-regional Secure Acceleration (Oversea Sites)
- Scheduling Traffic to EdgeOne by Performing Canary Switching
- Quickly Enabling HTTPS Access with EdgeOne Free Certificate
- Through traffic orchestration to multiple service providers
- EdgeOne facilitate APKs.s dynamic packaging of Android
- 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
- CreateL4Proxy
- ModifyL4Proxy
- ModifyL4ProxyStatus
- DescribeL4Proxy
- DeleteL4Proxy
- CreateL4ProxyRules
- ModifyL4ProxyRules
- ModifyL4ProxyRulesStatus
- DescribeL4ProxyRules
- DeleteL4ProxyRules
- CreateApplicationProxy
- ModifyApplicationProxy
- ModifyApplicationProxyStatus
- DescribeApplicationProxies
- DeleteApplicationProxy
- CreateApplicationProxyRule
- ModifyApplicationProxyRule
- ModifyApplicationProxyRuleStatus
- DeleteApplicationProxyRule
- Content Management APIs
- Data Analysis APIs
- Log Service APIs
- Billing APIs
- Certificate APIs
- Load Balancing APIs
- Diagnostic Tool APIs
- Custom Response Page APIs
- Version Management APIs
- Data Types
- Error Codes
- FAQs
- Agreements
- TEO Policy
- Contact Us
- Glossary
- Release Notes and Announcements
- Product Introduction
- Purchase Guide
- Description of 14-day Trial Plan Experience Benefits
- Billing Overview
- Basic Service Fees
- Value-added Service Fees
- Related Tencent Cloud Services
- Extra Package Description (Prepaid)
- Subscriptions
- Renewals
- Overdue and Expiration Policies
- Refund Policy
- Usage Cap Policy
- EdgeOne Plan Upgrade Guide
- Comparison of EdgeOne Plans
- Billing Usage
- About "clean traffic" billing instructions
- Getting Started
- Domain Service
- Site Acceleration
- Origin Configuration
- Edge Functions
- Overview
- Getting Started
- Operation Guide
- Runtime APIs
- Sample Functions
- Example Overview
- 301 Redirect
- Obtaining Client URL Information
- Customization Based on Client Geo Location
- Obtaining Client Geo Location Information
- Batch Redirect
- Returning an HTML Page
- Returning a JSON Object
- Fetch Remote Resources
- Authenticating a Request Header
- Modifying a Response Header
- Performing an A/B Test
- Setting Cookies
- Performing Redirect Based on the Request Location
- Using the Cache API
- Caching POST Requests
- Responding in Streaming Mode
- Merging Resources and Responding in Streaming Mode
- Protecting Data from Tampering
- Rewriting a m3u8 File and Configuring Authentication
- Adaptive Image Resize
- Image Adaptive WebP
- Customize Referer restriction rules
- Remote Authentication
- HMAC Digital Signature
- Naming a Downloaded File
- Obtaining Client IP Address
- Practical Tutorial
- Security Protection
- Overview
- DDoS Protection
- DDoS Protection Overview
- Exclusive DDoS Protection Usage
- Configuration of Exclusive DDoS protection Rules
- Web Protection
- Rules Template
- IP Groups
- Origin Protection
- Custom Response Page
- Alarm Notification
- Rule Engine
- L4 Proxy
- Data Analysis&Log Service
- Tool Guide
- Practical Tutorial
- Configuring EdgeOne Security Event Alarms via TCOP
- EdgeOne Resource Abuse Prevention
- EdgeOne Implementation of Session Persistence Based on Client IP Addresses
- EdgeOne Implementation of Origin-Pull Based on Client's Geo Location
- EdgeOne Hotlink Protection Practical Tutorial
- EdgeOne initiates Automatic Warm-up
- EdgeOne Automatic Cache Purge
- Cross-regional Secure Acceleration (Oversea Sites)
- Scheduling Traffic to EdgeOne by Performing Canary Switching
- Quickly Enabling HTTPS Access with EdgeOne Free Certificate
- Through traffic orchestration to multiple service providers
- EdgeOne facilitate APKs.s dynamic packaging of Android
- 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
- CreateL4Proxy
- ModifyL4Proxy
- ModifyL4ProxyStatus
- DescribeL4Proxy
- DeleteL4Proxy
- CreateL4ProxyRules
- ModifyL4ProxyRules
- ModifyL4ProxyRulesStatus
- DescribeL4ProxyRules
- DeleteL4ProxyRules
- CreateApplicationProxy
- ModifyApplicationProxy
- ModifyApplicationProxyStatus
- DescribeApplicationProxies
- DeleteApplicationProxy
- CreateApplicationProxyRule
- ModifyApplicationProxyRule
- ModifyApplicationProxyRuleStatus
- DeleteApplicationProxyRule
- Content Management APIs
- Data Analysis APIs
- Log Service APIs
- Billing APIs
- Certificate APIs
- Load Balancing APIs
- Diagnostic Tool APIs
- Custom Response Page APIs
- Version Management APIs
- Data Types
- Error Codes
- FAQs
- Agreements
- TEO Policy
- Contact Us
- Glossary
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.
Yes
No
Was this page helpful?