# CNAME and non-sending-domain

**URL:** <https://forum.dmarcian.com/t/cname-and-non-sending-domain/2844>\
**Category:** Community Area\
**Created:** [April 13, 2026, 10:25am UTC](https://forum.dmarcian.com/t/cname-and-non-sending-domain/2844 "2026-04-13T10:25:16Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Dante](https://avatars.discourse-cdn.com/v4/letter/d/f05b48/32.png) [@Dante](https://forum.dmarcian.com/u/Dante)\
**Post date:** [April 13, 2026, 10:25am UTC](https://forum.dmarcian.com/t/cname-and-non-sending-domain/2844/1 "2026-04-13T10:25:16Z")

</div>

I have a CNAME record set on a domain like “[domain.com](http://domain.com)”. I would like to use this same domain to send emails, but due to RFC limitations, I cannot set any type of TXT record on that domain. One solution could be to use the third-level domain “@mail.domain.com” for sending emails, setting the SPF1 record on that domain. However, if I want to make the second-level domain “[domain.com](http://domain.com)” a “non-sending domain”, I would have the same problem as before, being unable to set the “spf1 -all” policy because of the existing CNAME. What can I do?

---

<div class="post-metadata">

**Author:** ![LinkP](https://yyz2.discourse-cdn.com/flex036/user_avatar/forum.dmarcian.com/linkp/32/142_2.png) [@LinkP](https://forum.dmarcian.com/u/LinkP)\
**Post date:** [April 13, 2026, 1:20pm UTC](https://forum.dmarcian.com/t/cname-and-non-sending-domain/2844/2 "2026-04-13T13:20:28Z")

</div>

Welcome to the dmarcian forum.

Setting a CNAME at the apex like that violates the RFCs for exactly the reason you describe. The solution is to use A/AAAA records or move to a DNS provider that offers CNAME flattening or ANAME records.