Understanding Custom Hostnames

Application Performance
1

What is the name of the domain?

mycustomer com

What is the issue you’re encountering

Removing custom hostname from SSL have no effect

What are the steps to reproduce the issue?

I have a scenario where I have to create a Custom Hostnames for my clients. I have setup the DNS records on myhost.com for proxy fallback as below:

Type: CNAME
Name: proxy
Target: staging.myhost.com
TTL: Auto
Proxy status: Proxied

Then I created a DNS record for a client:

Type: CNAME
Name: customer1
Target: proxy.myhost.com
TTL: Auto
Proxy status: Proxied

In SSL/TLS → Custom Hostnames I mentioned the fallback origin as proxy.myhost.com. Then I added custom hostname www.mycustomer.com with TLS 1.3 and certificate type is Provided by Cloudflare with HTTP as validation method.
I then generated origin certificate and deployed on the server hosting www.mycustomer.com.
On my customer account I have created following CNAME record for mycustomer.com:

Type: CNAME
Name: www
Target: customer1.myhost.com
TTL: Auto
Proxy status: Not Proxied

I then visited the site www.mycustomer.com in the browser and it works fine. To test the working, I tried to delete the custom hostnames record and then visited the site again. It still works fine with SSL certificate.
I have checked the documentation also and its the recommended procedure to provide whitelabel domain to the customer.

My question is, what is the purpose of this adding custom hostnames when its still working without it? How can I thoroughly test its working?

2

It only works without custom hostnames if both domains are in the same Cloudflare account.

3

Thanks for the response. Yes I was previously testing in the same account. I have now used different account for customer and custom hostnames are now working as expected.

1 Like
4

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