- 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
Why do I get a CNAME and MX record conflict prompt when adding a DNS resolution record?
Take
example.com as an example.Record type | Host | Value |
MX | www | mx.mail.com |
CNAME | www | test.edgeone.com |
When performing a recursive resolution query, each record type has different priority, and CNAME has the highest priority. See RFC1034 and RFC2181. Therefore, during the resolution request process, the CNAME resolution record result will be returned first. When the host record value is the same, CNAME record and MX record cannot be configured at the same time, and you will get a prompt about the conflict.
If you do need to add CNAME and MX records at the same time when the host record is @, EdgeOne allows you to configure CNAME and records at the same time:
Record type | Host | Value |
MX | @ | mx.mail.com |
CNAME | @ | test.edgeone.com |
Reminder:
This configuration will lead to unstable mailbox reception. If the Local DNS of the mailbox server prioritizes the resolution of the CNAME type of the @ record, the resolution of the MX type of the @ record will be affected, resulting in a resolution failure. If the host record is not @ , but the MX and CNAME records still indicate a conflict, please refer to the description of other record type conflicts below.
Why do I get a CNAME and TXT record conflict prompt when adding a DNS resolution record?
Take
example.com as an example.Record type | Host | Value |
TXT | www | edgeone-txt-flag |
CNAME | www | test.edgeone.com |
The CNAME record has the highest priority, so if the host record is the same, configuring the CNAME record and the TXT record at the same time may cause the TXT record to fail to be parsed. In this case, EdgeOne will prompt record conflict.
If you do need to add CNAME and MX records at the same time when the host record is @, EdgeOne allows you to configure CNAME and TXT records at the same time:
Record type | Host | Value |
TXT | @ | edgeone-txt-flag |
CNAME | @ | test.edgeone.com |
Reminder:
This configuration will cause the TXT verification to fail, you can remove the CNAME record to solve this problem. TXT and CNAME records will still conflict when the host record is not @.
How do the record types conflict with one another?
See below for details:
✓: No conflict. When the HOST is the same, these two record types can both be configured. For example, after configuring the A record for
www.example.com, you can still configure the MX record.×: Conflict. When the HOST is the same, these two record types cannot be both configured. For example, after configuring the A record for
www.example.com, you can not configure the CNAME record.Record type | A | AAAA | CNAME | MX | NS | TXT | SRV | CAA |
A | ✓ | ✓ | × | ✓ | × | ✓ | ✓ | ✓ |
AAAA | ✓ | ✓ | × | ✓ | × | ✓ | ✓ | ✓ |
CNAME | × | × | × | × | × | × | × | × |
MX | ✓ | ✓ | × | ✓ | × | ✓ | ✓ | ✓ |
NS | × | × | × | × | ✓ | × | × | × |
TXT | ✓ | ✓ | × | ✓ | × | ✓ | ✓ | ✓ |
SRV | ✓ | ✓ | × | ✓ | × | ✓ | ✓ | ✓ |
CAA | ✓ | ✓ | × | ✓ | × | ✓ | ✓ | ✓ |
Note
The table above shows the conflict relationship when the HOST is not @. If the HOST is @, a CNAME record does not conflict with an MX or TXT record.
When the record type is A/AAAA/CNAME, can I configure both the resolution and acceleration when the HOST is the same?
Take the following configuration as an example:
Record type | Host | Value |
A | www | 1.1.1.1 |
A | www | 2.2.2.2 |
In this case, if you want to enable acceleration for one record, there will be a conflict. To enable acceleration for
1.1.1.1, you need to delete 2.2.2.2 first.Note
The above conflict happens on A/AAAA/CNAME records.
Which access ports are supported by default?
EdgeOne supports the access ports 80, 8080, and 443 by default.
What happens if there are multiple A/AAAA/CNAME records with the same host record name and no weights are set?
If there are multiple A/AAAA records with the same host record name and no weights are set, all the A/AAAA records will be returned. If there are multiple CNAME records with the same host record name and no weights are set, one of the CNAME records will be returned using a round-robin method.
Yes
No
Was this page helpful?