Enabling O2O on zone and how to implement for Shopify
Hi,
I have read up on the article: https://developers.cloudflare.com/cloudflare-for-platforms/cloudflare-for-saas/saas-customers/provider-guides/shopify/
Firstly, I'm looking to set up O2O for my domain and wanted to check whether it needs enabling on a Cloudflare account level?
Secondly, the domain is currently set up on Cloudflare using non-proxied dns records for Shopify. A record and CNAME, both set to DNS only.
To enable O2O, what steps do I need to take?
Once O2O is enabled on the account, do I simply switch to proxied records for both the A and CNAME? Or do I leave these as they are and add the proxied record as per the article:
CNAME
<YOUR_SHOP_DOMAIN>
shops.myshopify.com
Proxied
If so, what domain should replace the <YOUR_SHOP_DOMAIN>? xxxxx.myshopify.com domain or my actual shop domain?
Docs just seem a little unclear.
Many thanks
12 Replies
Did anybody have any advice on this? New to discord, so wasn't 100% if I had posted correctly...
To enable O2O on your account, create a CNAME DNS record.
O2O setup should happen automatically on Shopify’s side, assuming you have informed them that you wish to add the domain in question as a Custom Domain
As for the CNAME record itself it is shop.yourdomain.com pointing toward the record Shopify gives you. You decide which (sub)domain to put it on
Idk why the whole thing is in quotes tbh
Only the first part is supposed to beI think shopify is using cloudflare.
Indeed they are
this was escalated on forums from forums post for o2o acceess
Once it is enabled, the answer is CNAME to
shops.myshopify.com Proxied. If you have any existing A record for shopify, change them overSo currently I have the following records:
A | @ | 23.227.38.32 | DNS only
CNAME | www | shops.myshopify.com | DNS only
once shopify's special o2o is enabled on your acct, you'd want
CNAME | @ | shops.myshopify.com | Proxied CNAME | www | shops.myshopify.com | Proxiedthat is, if you wanted your own zone settings/customizations on both
@Chaika OK, thanks for confirming
O2O only works off CNAMEs. It doesn't understand A records, it'd just continue to not apply your config if you use them, proxied or not
Thats great, I'm hoping to utilise Cloudflare to help protect the site from bots, we are getting so many page visits from bots at the moment and i'm hoping having cloudflare proxied I can utilise the options available to help prevent or atleast reduce
Scott enabled O2O. Interestingly he sort of said to use an A record for root, I know for a fact that doesn't work on the latest CF For SaaS stuff but Shopify's setup and O2O stuff is special, maybe it does. You could try it with a proxied A record and switch if it doesn't work, or use a cname from the start, doesn't matter, CF will flatten it since it's proxied eitherway
I will give both a go and report back
After also receiving a response from Matthew Bullock directly via emailI along with supporting material, he suggested using the following records, which have worked:
CNAME | @ | shops.myshopify.com | Proxied
CNAME | www | shops.myshopify.com | Proxied
Thanks everyone for your help on this matter, everything seems to be working! 🙌🏼
Now on to blocking specific traffic!
Hey @Boldr I hope your bot battle is going well, I'm having the same trouble with my Shopify and can't seem to set up this O2O to stop them. I'm going in circles, banging my head on the desk but I know it's possible and this post gives me hope that I will figure it out.