Allow customers to add CNAME pointing to our domain without using workers

What is the name of the domain?

customer1.com CNAME pointing to customer1.mydomain.com and customer2.com CNAME pointing to customer2.mydomain.com

What is the issue you’re encountering

Is there any way to allow other users to CNAME records to our domains having SaaS for custom hostname but without using workers as workers may have bottleneck? Currently I am using workers to resolve the request but this is just overhead. Can I have other alternative for this assuming I may have multiples customers adding CNAME to our record.

What steps have you taken to resolve the issue?

Currently I am using workers on route based trigger to trigger the worker and using custom hostname to get certificate. But I want to remove workers as it is just bottle neck.

What feature, service or problem is this related to?

DNS records

You want to allow customers to use CNAME records with your SaaS solution for custom hostnames without the overhead of Workers. You can simply Eliminate Workers and enable CNAME for custom domains without bottlenecks.

Can you explain why you believe that you need Workers?

1 Like

Have you managed to resolve this? I’m currently looking to have user pointing a CNAME at my domain as well. Though I haven’t looked to use workers.

I have read somewhere online that support are able to disable this protection on your domain but it didn’t give details on how you would go about getting that sorted with support.

1 Like

This used to be an option, but has now been replaced by Cloudflare for SaaS…

(The OP wants to proxy their customers’ apex domain, so that would require an Enterprise plan add-on)

2 Likes

For a single CNAME, I saw documentation about fallback URL however I want to have multiple CNAME pointing to multiple subdomain with in the cloudflare. I am using using cloudflare proxy so the cloudflare is blocking the direct access using CNAME.

I don’t want to use apex domain, however I want to provide CNAME access to my domain for client to add in theirs.
So only possible way I have been finding is using workers which I think is not required therefore want to bypass workers, by using only custom hostname. Therefore I am trying to find some possible ways.
I think I read somewhere enterprise will allow to remove this restriction as well, is this true?

Do you want to route all custom hostnames to the same server or to different servers? Different servers would require Workers or an Enterprise plan. One server can be done without.

2 Likes

Can you tell me about the cost for enterprise including this as I couldn’t find the exact costing. And also will they remove this restriction if I have enterprise plan?

Enterprise plans are customised according to your needs so you will need to contact Cloudflare Sales for a quote. It will be several thousand USD per month upwards depending on the package.

2 Likes

Out of curiosity, how would you do it where it is all routed to a single server?

That is explained in the docs:

1 Like

This topic was automatically closed 15 days after the last reply. New replies are no longer allowed.