{"id":2613,"date":"2019-10-22T17:24:10","date_gmt":"2019-10-22T09:24:10","guid":{"rendered":"https:\/\/www.mondoze.com\/guide\/?post_type=kb&p=2613"},"modified":"2022-10-05T08:02:45","modified_gmt":"2022-10-05T00:02:45","slug":"understand-and-configure-cname-flattening","status":"publish","type":"kb","link":"https:\/\/www.mondoze.com\/guide\/kb\/understand-and-configure-cname-flattening","title":{"rendered":"Understand and configure CNAME Flattening"},"content":{"rendered":"\t\t
Per DNS specifications (RFCs), a domain cannot have a\u00a0CNAME record<\/em>\u00a0and another DNS record of a different type if both records would share the same name. configure CNAME Flattening DNS RFCs also require an MX record<\/em>\u00a0to correspond to a related\u00a0A record<\/em>\u00a0and not a\u00a0CNAME<\/em>. This is problematic when you need a\u00a0CNAME<\/em>\u00a0for your root (for example, a\u00a0CNAME<\/em>\u00a0from example.com to example.herokuapp.com) but also need another type of DNS record at the root domain such as an\u00a0MX record<\/em>\u00a0for mail delivery.<\/p> Typically, the aforementioned situation would cause problems receiving email. However,\u00a0CNAME Flattening <\/strong>ensures the chain of\u00a0CNAMEs<\/em> is follow to an A<\/em>\u00a0or\u00a0AAAA<\/em>\u00a0record to allow mail delivery while still adhering to DNS RFCs. The\u00a0CNAME<\/em>\u00a0responses are cached and DNS TTLs are respected.<\/p> CNAME Flattening<\/strong>\u00a0still works if the corresponding DNS\u00a0CNAME record<\/em> is “grey cloud” in the DNS<\/strong>\u00a0app of the Cloudflare dashboard.<\/p> CNAME Flattening<\/strong> cannot be disable. By default, domains are setup to only flatten\u00a0CNAME records<\/em>\u00a0at the root domain.<\/p> Domains on Pro, Business and Enterprise plans can either apply\u00a0CNAME Flattening<\/strong>\u00a0to\u00a0CNAMEs<\/em>\u00a0at the root domain or for all\u00a0CNAMEs<\/em>\u00a0within the domain. To flatten all\u00a0CNAMEs<\/em>\u00a0in the domain, select Flatten all\u00a0CNAMEs <\/em>from the\u00a0CNAME Flattening<\/strong>\u00a0dropdown menu within the\u00a0DNS<\/strong>\u00a0app of the Cloudflare dashboard.<\/p> Free plans can only flatten\u00a0CNAMEs<\/em>\u00a0at the root domain.<\/p>\t\t\t\t\t<\/div>\n\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t<\/div>\n\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t<\/section>\n\t\t\t\t\t\t<\/div>\n\t\t\t\t\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t","protected":false},"excerpt":{"rendered":" Understand and Configure CNAME Flattening How CNAME Flattening works Per DNS specifications (RFCs), a domain cannot have a\u00a0CNAME record\u00a0and another DNS record of a different type if both records would share the same name. configure CNAME Flattening DNS RFCs also require an MX record\u00a0to correspond to a related\u00a0A record\u00a0and not a\u00a0CNAME. This is problematic when …<\/p>\nHow to change settings for CNAME Flattening<\/strong><\/h3>