<example>.netis pointted to cloudflare DNS &
<example>.comis managed by external register & DNS server.
test.<example>.netis registered A record in cloudflare DNS with proxy mode &
Welcome to the Cloudflare Community.
As you have learned, you cannot use CNAMEs in the manner that you have. A CNAME has two parts, the alias and the canonical name. The webserver listening on the host at the canonical name must be configured to respond to requests that contain the alias in the HTTP host headers. Since your canonical name is proxied, you reach the Cloudflare proxy rather than the origin server when you use the alias. The Cloudflare proxy does not have any configuration for the alias and will fail to deliver the response you want.
The short answer is that configuration will never work as it is invalid.
Thank you for the reply,
Could you please suggest how we can configure in this scenario as below.
.com is managed by external DNS server. (unambe to managed by cloudflare DNS)
.net will be managed by cloudflare DNS server.
want to serve .com .net via same backend.
Why not redirect one to the other? There is no benefit to serving duplicate content on multiple domains. Search engines typically impose a penalty on such a configuration.
You might be able to achieve your desired outcome with Cloudflare for SaaS.
Thank you, This helps
This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.