On this page

Show all

Help Center/ Domain Name Service/ FAQs/ Public Zones/ How Do I Handle the Conflict Between CNAME and MX Record Sets?

How Do I Handle the Conflict Between CNAME and MX Record Sets?

Updated on 2024-03-13 GMT+08:00

View PDF

Background

If your enterprise purchases a domain name for end users to access the website of your enterprise and for employees to access the office mailbox of your enterprise. Appropriate record set configuration is necessary.

For access acceleration or secure purposes, cloud services such as CDN, WAF, and OBS are configured for the website. In this case, A record sets cannot be configured to map the domain name to the IP address of the website. Instead, CNAME record sets are required to map the domain name to the domain name of the cloud service such as CDN, WAF, or OBS. The standard DNS protocol does not allow the same domain name to have both CNAME record sets and other types of record sets such as MX record sets at the same time. If a domain name is used for accessing the website and for accessing the enterprise office mailbox as well, the mailbox may be unavailable when there is a conflict between CNAME record sets and MX record sets.

If this happens, refer to this FAQ to solve the problem. Domain name example.net is used as an example here.

(Recommended) Universal Solution

Accessing a website

Add an A record for mapping example.net to the IP address of the website. For details, see Adding an A Record Set.
Add a CNAME record set for mapping www. example.net to the domain name of the cloud service such as CDN, WAF, or OBS. For details, see Adding a CNAME Record Set.
Configure 301/302 redirection for the website IP address to redirect example.net to www. example.net.

Accessing a mailbox: Add an MX record set and an A record set for example.net. The MX record set configured for example.net does not conflict with the A record set. For details, see Adding an MX Record Set.

(Not Recommended) Alternative Solution

If 301/302 redirection cannot be configured and you want both a CNAME record set and an MX record set to be configured for the domain name, the office mailbox of your enterprise may become unavailable.

If a local client first accesses the website using example.net, the domain name is mapped to www.example.net.c.cdnhwc1.com (domain name of CDN). The local DNS server caches the CNAME value based on the TTL. If at this time the local client accesses the mailbox, the MX record set configured for example.net is requested. Because the local DNS server has already cached the CNAME value of example.net, the local DNS directly returns www.example.net.c.cdnhwc1.com. As a result, the request to the MX record set fails. The email sending and receiving of the mailbox is affected and will restore only after the cache of the CNAME value expires.

You can refer to the following configuration:

Accessing a website: Add a CNAME record set for example.net to map the domain name to the domain name of the cloud service such as CDN, WAF, or OBS.

Accessing a mailbox: Add an MX record set for example.net using a different line to avoid conflicts with the CNAME record set.

WARNING:

This solution cannot prevent the situation where the mailbox may become unavailable. Evaluate the risks carefully.

Parent topic: Public Zones

Feedback

Was this page helpful?

Helpful Not helpful

Provide feedback

Thank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.

The system is busy. Please try again later.

Which of the following issues have you encountered?

Content is inconsistent with the product UI

Unclear descriptions

Lack of examples or code

Incorrect steps

Can't find what I need

Lack of best practices

Feedback (optional)

0/500

Select at least one type of issue, and enter your comments or suggestions.

Enter a maximum of 500 characters.

Submit Cancel

For any further questions, feel free to contact us through the chatbot.

Chatbot