This was posted somewhere behind a membership wall. So I thought I’d post this to the public.
I think this is correct for the CName Strategy in Cloudflare:
Type: A, Name: Cloud, IP Content:188.8.131.52, Proxy Status: off, TTL: Auto
Type: CName: Name: website.xyz, Content: cloud.website.site, Proxy Sttus: Off, TTL: Auto
My only question is can we turn on proxy when doing CName Flattening.
Someone had responded saying this is not CNAME flattening. But it actually is CNAME flattening.
CNAME flattening allows you to create a CNAME record at the root of your domain without violating RFC’s (the rules that govern the Internet). Here at DNS Made Easy, we call these ANAME records… but we’ll get to that in a minute.
Since website.xyz is the apex (@), and you’re using a CNAME record pointing to cloud.website.site, this is effectively CNAME flattening. Cloudflare will query the record cloud.website.site for it’s IP and return it for anyone that queries website.xyz
With CNAME flattening, Cloudflare finds the IP address that a CNAME points to . This process could involve a single lookup or multiple (if your CNAME points to another CNAME ). Cloudflare then returns the final IP address instead of a CNAME record, helping DNS queries resolve up to 30% faster.
Typically you don’t proxy the original record cloud.website.site unless it’s actually serving traffic. It should be used for anything other than mapping domains to it so that you could potentially swap all domains to a different server.
You might also run into
Error 1014: CNAME Cross-User Banned