Marvin
Explore posts from serversCDCloudflare Developers
•Created by juanferreras on 5/16/2024 in #general-help
With Delegated DCV validation, do I need just the root CNAME or one per each hostname?
Solved:
I managed to fix it by setting the worker route to "*/*" instead of "*.example.com/*".
Original for future reference:
Hey @juanferreras, I think I have a similar issue and the docs are very confusing. How did you setup everything?
I have a multi-tenancy app where the custom domain of the customer should point to the correct subdomain of my app like:
test.custom.com -> tenant1.example.com
I have setup the DNS records on example.com like this:
A
proxy-fallback
192.0.2.1
CNAME
*
proxy-fallback.example.com
I also enabled "custom hostnames", set the fallback origin and added the custom hostname of the customer:
Fallback Origin:
proxy-fallback.example.com
Custom hostname:
test.custom.com
The two TXT + CNAME are also added in the DNS of custom.com:
TXT
_acme-challenge.test
<token>
TXT
_cf-custom-hostname.test
<token>
CNAME
test
tenant1.example.com
Everything is green and with status "active" but it still doesn't work when I open "test.custom.com". It loads forever and then shows a Cloudflare 522 error.
When I open "tenant1.example.com", it shows the site though.
Any idea what could be the issue here? Maybe I'm missing a setting somewhere?
For the site, I'm using a CF Worker which just shows a "Hello World" HTML text. The wildcard domain "*.example.com/*" is mapped to the worker via "Workers Routes".
The original domains are of course not "custom.com" or "example.com", but a .co and .com domain. Both registered with Cloudflare.
7 replies