(forgive the … in domain examples, this form wont let me add links)
I’m working on a simple static web hosting service, using S3 SDK and CloudFlare API to create zones and buckets on the fly for users to host static websites on.
My DNS knowledge isn’t great, but I was hoping I could setup something like this:
My domain name (example) of hosting.com is on CloudFlare.
Each user/site created via my app would get it’s own “endpoint” such as user…hosting…com
user.hosting.com would CNAME to the s3 bucket endpoint, such as my…custom…domain…s3-website-eu-west-1…amazonaws…com
Then, I would simple ask users to add a CNAME on their own domain (my…custom…domain), and point it at user≥.hosting…com, which would then route to the bucket.
I intended on having a CNAME in my CloudFlare account for every user, which worked when working with other CloudFlare accounts. But I see now that if they use another DNS service, such as Fasthosts, the CNAME fails as CloudFlare can’t understand where to point the domain name.
Is there a solution for this? I’ve seen something about managed CNAMEs which is enterprise only, then there’s also mention of partial CNAMEs for partners.
Would either of those work? or does anybody have any other ideas?
I hoped to use as many of CloudFlare’s features as possible (CDN, SSL, DdoS protection etc.) without needing to run any servers. In essence, I would simply be creating s3 buckets, with CloudFlare DNS, that users could point their own subdomain (or root domain) at.