Need help enabling O2O for proxied CNAME DNS record

What is the name of the domain?

What is the error number?

No error number encountered

What is the error message?

Target is not allowed for a proxied record

What is the issue you’re encountering

Need help enabling O2O for proxied CNAME DNS record

What steps have you taken to resolve the issue?

Attempted to create a proxied CNAME record, but it failed with the error: ‘Target xxxxx is not allowed for a proxied record.’ Reviewed Cloudflare’s documentation and community forums and determined that I need to request O2O enabled for my account

What are the steps to reproduce the issue?

From the Dashboard: DNS>Records>Add record
Type - CNAME Name – my domain
Target – Shopify targe domain
Proxy status - Proxied
Save - This is where I see the error

Screenshot of the error

Lately a helpful post:

From the shared screenshot, it looks to me like you’ve got A type DNS record already added.

Are you going to be using CNAME or A type of the DNS records pointed to the Shopify?

May I ask if you’ve followed the instructions from article below to enable Shopify for your domain at Cloudflare? :thinking:

Helpful:

O2O will work automatically on proxied CNAMEs anyway so doesn’t need to be enabled by Cloudflare manually. Just ensure you are using your provider’s CNAME and not A/AAAA records.

It has to be either one (CNAME) or another (A), cannot be both variations.
Sometimes it works perfectly fine even with :grey: (DNS-only) since Shopify uses Cloudflare, therefrom no need for proxy :orange: .

Hey @fritex thanks for following up. Yes I have removed the A type entry and added CNAME to shops.myshopify.com. I realised after I uploaded the screen shot last night that I still had the A type in place. This has now been removed.

Additionally, I can confirm I am following the instructions. Thank you.

Thanks for confirming! I’ve enabled O2O for your account, could you try the action again?

Great, thanks @mattlab I can confirm I can now set the CNAME entry to proxied. I’ve rolled it back to DNS for now whilst I double-check the settings and confirm everything is in order. But you can certainly consider this resolved, and I’ll be sure to refer to the documentation and forums if I encounter any further issues.

Thanks again for the speedy response, greatly appreciated!

1 Like

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.