4 ms·

Yes, custom domains. Cloudflare requires the domain DNS to be handled through Cloudflare. Pretty annoying if you for some reason has to stick with another DNS

Yes, custom domains. Cloudflare requires the domain DNS to be handled through Cloudflare. Pretty annoying if you for some reason has to stick with another DNS provider, but would like to use pages. Guess I might look into Gitlab pages instead.

rexf 4y ago
yup, using netlify was way easier for my custom domain. I looked into cloudflare pages, but I didn't want to move my domain (DNS) over to cloudflare
e63f67dd-065b 4y ago
I didn't realise that Cloudflare DNS was such a deal breaker. Is there a reason to prefer something other than CF for DNS? I've always used CF DNS and I've never felt like I'm missing anything. Edit: I also just checked the docs and it looks like you should be able to just CNAME to a `something.pages.dev`; why doesn't that work with another provider, or am I missing something?
- spyke112 4y ago
  Legacy reasons I guess. I this case it's a matter of a client not wanting to move off e-mail they use through their shared hosting provider, and me not wanting to touch that hornets nest. I'm fine with just setting up a CNAME record pointing somewhere, but I really do not want to change their DNS provider. As mentioned by someone else, last I tried, CF refused to "finalize" the setup and start building before I had setup the domain. I may have missed something though, I'll have to check again.
stavros 4y ago
I don't think so? I set one up last night and it waited for me to change my DNS. My domain was through them, so it happened automatically, but there was nothing saying it had to be.
mfsch 4y ago
Looks like this is the case for apex domains, but not for subdomains, for which you simply need to configure a CNAME record: https://developers.cloudflare.com/pages/platform/custom-domains/ https://developers.cloudflare.com/pages/platform/custom-doma...

4 ms·

Yes, custom domains. Cloudflare requires the domain DNS to be handled through Cloudflare. Pretty annoying if you for some reason has to stick with another DNS

by spyke112 4y ago

rexf 4y ago
yup, using netlify was way easier for my custom domain. I looked into cloudflare pages, but I didn't want to move my domain (DNS) over to cloudflare
e63f67dd-065b 4y ago
I didn't realise that Cloudflare DNS was such a deal breaker. Is there a reason to prefer something other than CF for DNS? I've always used CF DNS and I've never felt like I'm missing anything. Edit: I also just checked the docs and it looks like you should be able to just CNAME to a `something.pages.dev`; why doesn't that work with another provider, or am I missing something?
- spyke112 4y ago
  Legacy reasons I guess. I this case it's a matter of a client not wanting to move off e-mail they use through their shared hosting provider, and me not wanting to touch that hornets nest. I'm fine with just setting up a CNAME record pointing somewhere, but I really do not want to change their DNS provider. As mentioned by someone else, last I tried, CF refused to "finalize" the setup and start building before I had setup the domain. I may have missed something though, I'll have to check again.
stavros 4y ago
I don't think so? I set one up last night and it waited for me to change my DNS. My domain was through them, so it happened automatically, but there was nothing saying it had to be.
mfsch 4y ago
Looks like this is the case for apex domains, but not for subdomains, for which you simply need to configure a CNAME record: https://developers.cloudflare.com/pages/platform/custom-domains/ https://developers.cloudflare.com/pages/platform/custom-doma...