3 ms·

Does anyone know if you can use a Cloudflare tunnel on a single subdomain without using Cloudflare on everything else? It seemed like I had to run everything o

Does anyone know if you can use a Cloudflare tunnel on a single subdomain without using Cloudflare on everything else? It seemed like I had to run everything on the domain through Cloudflare when I looked into this in the past. That might be fine in the end, but I just wanted to try tunnels out first without committing to anything else. Edit: thanks, everyone! This was just going to be a tiny web site for hobby purposes at first.

deleted 5y ago
[deleted]
ejcx 5y ago
(I work at Cloudflare). You can sign up just a subdomain (sub.foo.xyz) as an enterprise customer and then add an NS records from your DNS provider to Cloudflare for that subdomain. Tunnels also has a testing domain you can use. It should give you a subdomain like xxx-xxx-xxx.trycloudflare.com for basic "How do I get this thing working" testing.
- hellodear437 5y ago
  helo
judge2020 5y ago
Unless you want to pay for the business plan with a CNAME Setup[0], you do need to use their DNS offering, even if the rest of your site's DNS records are 'unproxied'. If you just want to try tunnels at all, with a non-descript hostname, Tunnel gives out subdomains that end in trycloudflare.com[1]. If you're referring to the TOS issue that is often discussed here, it depends on what that subdomain is, since Cloudflare doesn't just want to be pushing binary data for free. If the subdomain is some website that is primarily used in the browser, CF will generally be fine leaving it up even if you push TBs a day, but if it's just a file host CF has been known to flag that for abuse and disable proxying for the domain[2]. As for why they bother with a free plan with such cryptic rules, their S1 explains it[3]. 0: https://support.cloudflare.com/hc/en-us/articles/360020348832-Understanding-a-CNAME-Setup#h_48897892411544043189831 https://support.cloudflare.com/hc/en-us/articles/36002034883... 1: https://developers.cloudflare.com/cloudflare-one/connections/connect-apps/run-tunnel/trycloudflare https://developers.cloudflare.com/cloudflare-one/connections... 2: https://community.cloudflare.com/t/the-way-you-handle-bandwidth-over-usage/42969/2?u=judge https://community.cloudflare.com/t/the-way-you-handle-bandwi... 3: https://l.judge.sh/85EH https://l.judge.sh/85EH (I am not a CF employee nor your lawyer)
carride 5y ago
You can have cloudflare handle your DNS, though nothing more. Each DNS record has an extra setting to Proxy. For the tunneled CNAME the proxy must be turned on. For anything else to be pass though traditional DNS then set the Proxy setting off. *edit: Learned here in this discussion that moving NS servers to Cloudflare is not even required. I’ll need to test that.

deleted 5y ago

[deleted]

ejcx 5y ago

(I work at Cloudflare). You can sign up just a subdomain (sub.foo.xyz) as an enterprise customer and then add an NS records from your DNS provider to Cloudflare for that subdomain. Tunnels also has a testing domain you can use. It should give you a subdomain like xxx-xxx-xxx.trycloudflare.com for basic "How do I get this thing working" testing.

hellodear437 5y ago
helo

judge2020 5y ago

Unless you want to pay for the business plan with a CNAME Setup[0], you do need to use their DNS offering, even if the rest of your site's DNS records are 'unproxied'. If you just want to try tunnels at all, with a non-descript hostname, Tunnel gives out subdomains that end in trycloudflare.com[1]. If you're referring to the TOS issue that is often discussed here, it depends on what that subdomain is, since Cloudflare doesn't just want to be pushing binary data for free. If the subdomain is some website that is primarily used in the browser, CF will generally be fine leaving it up even if you push TBs a day, but if it's just a file host CF has been known to flag that for abuse and disable proxying for the domain[2]. As for why they bother with a free plan with such cryptic rules, their S1 explains it[3]. 0: https://support.cloudflare.com/hc/en-us/articles/360020348832-Understanding-a-CNAME-Setup#h_48897892411544043189831 https://support.cloudflare.com/hc/en-us/articles/36002034883... 1: https://developers.cloudflare.com/cloudflare-one/connections/connect-apps/run-tunnel/trycloudflare https://developers.cloudflare.com/cloudflare-one/connections... 2: https://community.cloudflare.com/t/the-way-you-handle-bandwidth-over-usage/42969/2?u=judge https://community.cloudflare.com/t/the-way-you-handle-bandwi... 3: https://l.judge.sh/85EH https://l.judge.sh/85EH (I am not a CF employee nor your lawyer)

carride 5y ago

You can have cloudflare handle your DNS, though nothing more. Each DNS record has an extra setting to Proxy. For the tunneled CNAME the proxy must be turned on. For anything else to be pass though traditional DNS then set the Proxy setting off. *edit: Learned here in this discussion that moving NS servers to Cloudflare is not even required. I’ll need to test that.