Cloudflare error 1014 CNAME Cross User Banned

[Fyhrer]

Website URL

https://pylearn.eu.org

Error Message

Error 1014 - CNAME Cross-User Banned

Other Information

I have never seen this error before. I suspect it might be due to my Cloudflare configuration?

But then again, I don’t think this is the problem, since I’ve used this same configuration on all of my previous Custom domains. Im suspecting that the new update where to add a custom domain to your account, it needs to share the same hosting account with a regular subdomain.

This main domain is shared by 2 websites, my other private website and the website that’s throwing this error.

[Greenreader9]

Correct. Follow this to set it up correctly.

Also, please remember that you are only allowed to have 3 free hosting accounts, no matter how many email accounts you have registered with the service. If an Admin finds you have more then 3, all of them will be permanently suspended.

A Full Guide To Cloudflare

Hello, I will show you how to easily set up Cloudflare, Edit Records, and Troubleshoot with images! PLEASE READ BEFORE STARTING!!! Cloudflare cannot be used on free subdomains from InfinityFree. You can use Cloudflare on Custom Domains (yoursite.com) and with Custom Sub-Domains (subdomain.yoursite.com). A video tutorial can be found at the end of this guide, should you get stuck. You must connect your domain to your InfinityFree account first. Read more here. Set-Up Cloudflare Go to Dash…

[Admin]

This issue has nothing to do with the change in account creation flow. I recognize the error, and I can tell you that it’s basically a side effect of us using infintyfree.com for the main domains.

---

When you have your DNS at Cloudflare, the DNS records that are actually published for your domain (e.g. pylearn.eu.org) are pointing to Cloudflare, not the IP address that’s configured in Cloudflare.

Normally, if you create a CNAME record, like pointing www.pylearn.eu.org, then normally, visitors will lookup www.pylearn.eu.org, see that it has a CNAME pointing to pylearn.eu.org, get the IP address of pylearn.eu.org, and connect to that IP address.

But with Cloudflare, www.pylearn.eu.org will also point to Cloudflare’s IPs from the perspective of visitors.

If Cloudflare would then do a standard DNS lookup, then visitors connect to www.pylearn.eu.org at Cloudflare, which would lookup pylearn.eu.org, which is Cloudflare, so Cloudflare would connect to Cloudflare before going to your actual hosting account.

That’s of course not what you’d expect to happen. So Cloudflare internally looks up the IP address of pylearn.eu.org, and when a request comes in for www.pylearn.eu.org, directly connects to the actual IP address that pylearn.eu.org point so.

All of this is what you’d expect.

But what if you now pointed your domain with a CNAME record to someone else’s website on Cloudflare? Now this “sensible” approach is no longer sensible. Because that other website owner may be using Cloudflare to control access to their website. So then that other website owner wouldn’t want you to use your domain with your Cloudflare settings to connect to their backend server. That would be a huge security problem for that other website.

To plug this hole, Cloudflare doesn’t blindly grab the backend IP, it only lets you CNAME to other Cloudflare hosted websites on the same account. If the CNAME points to a domain on another account, you get this error you see here.

---

The domain infinityfree.com is hosted at Cloudflare. But it’s hosted on our Cloudflare account, not yours, so Cloudflare blocks these cross account lookups.

---

The reality is that this “CNAME to main domain” approach which we used to recommend in the past just doesn’t work with infinityfree.com main domains and never has, regardless of which DNS provider you use. You should just configure the website IP directly in your nameservers.

[Fyhrer]

I followed the guide but there’s 1 website ip being shared for 2 websites? What would i do here? just use that ip?

[KangJL]

It is better to use A record for your case.
Using CNAME record will just mess up your dns entry.
So read the guide which Greenreader9 has provided

[Admin]

Yes, exactly.

You were pointing multiple websites to the same IP already to begin with. DNS just translates domain names into IP addresses. Whether you use a CNAME or a direct IP address makes no difference for how people connect to your website.