What is the name of the domain?
What is the issue you’re encountering
CNAME showing not existing yet they do exist
What feature, service or problem is this related to?
DNS records
If the CNAME is proxied then it will return Cloudflare IP addresses in A/AAAA records. If the CNAME needs to be validated by a web host or mail provider, you will need to set it to “DNS only” instead of “Proxied”.
If the CNAME is for the apex domain majentasolutions.com then Cloudflare will flatten it to IP addresses anyway as CNAMEs at the root aren’t permitted for public DNS.
If unsure can you give the DNS record that uses the CNAME?
the CNAME’s are portal.majentasolutions.com and xylem.majentasolutions.com
Both are proxied so Cloudflare IP addresses will be returned, see…
If you, or the host, needs to see the CNAME to validate it, change the DNS records to “DNS only”. Requests will go direct to the origin server and not pass through Cloudflare through, so no Cloudflare features or protections will be applied in that case.
would this make any sense to why it suddenly broke? Sorry, I’m new to this:
‘changed the DNS records to match what webflow requires. also changed the SSL on Cloudflare to flexible as webflow requires that’ … could that be the cause of the problem and why it suddenly became an issue?
The DNS resolution isn’t the issue, it’s doing what it should. Likely for Webflow you need to set the records for “DNS only” so requests go direct to them. Do not use “Flexible” as an SSL/TLS setting, use only “Full (strict)”.
1 Like
This topic was automatically closed 15 days after the last reply. New replies are no longer allowed.