So here’s my current setup - I’m using cargo.site, (It’s a CMS, and I bought my domain through them, so in turn it’s through a reseller) they have a DNS editor, but I can’t add any CNAME’s, etc. So what I’ve done is proxied the origin IP’s through CF, then add the NS through the CloudFlare dashboard.
My question is, with this, can I use all of CloudFlare’s tools? Still seems like there’s some lagging issues, etc.
I guess I could theoretically transfer the domain, and do a 301 redirect? Upon Googling, it does say I can still use CloudFlare without the NS pointing within the origin.
Then I should take the domain, to the original provider, and get it out of Cargo? Since Cargo will not allow me to point the NS to the ones Cloudflare assigned. Some of the information they gave me, was pretty vague.
If you then want to connect the domain back to Cargo, without using our nameservers, you can do so using the alternate CNAME method (which is the only non-nameserver method we have on Cargo 2). The complete instructions for what you need to do are (in order):
In your registrar’s control panel, modify the existing CNAME entry for www (or create a new one, if it doesn’t exist already), to have it point to subdomain.cargocollective.com. Use that address exactly - do not change it in any way , as that’s the specific and correct record that needs to be there, not anything else.
Still in your registrar’s control panel, add a 301 redirect, which points example.com to www.example.com (change these to your actual domain, of course).
Enter www.example.com (your actual domain, though) in the Cargo admin, under “Use an existing Domain Name”, then “Enter a Third-Party Domain” (paste the domain in there and hit the “enter” key on your computer keyboard).