I’m using Siteground (SG) now for hosting, where you can setup Cloudflare (CF) through SG’s cPanel, however it REQUIRES your site resolve as www which blew my mind. I took it off CF CDN through Siteground, re-added in CF and pointed my nameservers straight to CF.
All was well for 24 hours, now my site is down. I called Siteground, they said I had to add www in my DNS settings in CF, either as an A Record or CNAME. They said it should be back up in @10 minutes afterward. It’s not yet, but even if it is, I want there to be a public resource for this; I can’t be the only one who wants a naked domain while using CF’s CDN.
Is it normal that there’s not a record for www automatically? Is that an A record everyone with a naked domain will need to add manually?
Should that A record be an “orange cloud” with HTTP proxy?
Is there anything else we need to know when doing a naked domain with a CDN?
Right, that’s what I’m doing, but how was I supposed to know that I needed to add a DNS record for “www”? Why wasn’t there there automatically? Where are the instructions informing anyone that they need to add a record for “www”?
www records aren’t a required thing. They only need to exist if they are being used and if they are supposed to point to something. If at the time you added your domain to Cloudflare directly the www was in use by siteground, the true origin IP address was obfuscated and Cloudflare couldn’t add it for you. During the signup process a list of records imported is presented along with test to verify all the needed ones were there.
I firmly believe, it would be already added since you updated your nameservers.
I would repeat my answer … If you use Cloudflare from cPanel option, it wont work for non-www version. It will work only for www version due to its limitation, this has been clearly stated in Siteground docs.
If you want to use Cloudflare there are two options
Either switch to Cloudflare manually, avoid cPanel way. (I would recommend this way)
Sign up Cloudflare with new email > add your domain > update new namservers . . .