gitbook and digital ocean domain verification fails when multiple CNAME records exist
We have just changed our project domain. All our apps are moving from subdomains on website1.com to website2.com
To work with gitbook and digital ocean, we have several CNAME subdomain records (proxied) to the gitbook page or digital ocean app. I have deleted those record, and added the record to the website2.com but both are complainng they cannot verify.
I think this is something to do with the "Error 1014" CNAME Cross-User Banned cloudflare error - indicating that Cloudflare sees that two different accounts (website1 and website2) have the same CNAME record even though it is deleted for many days now. See https://docs.tonomy.io which should point to gitbook.
How can I fix this?
11 Replies
Gitbook uses CF For SaaS, you'll see that error if you don't properly setup the Custom Domain on their end. Did you readd the domain on their end/what's the status there?
ah you edited it with the new domain name, which was the old?
yes ive deleted and re-added the domain several times in both gitbook and Digital Ocean. The CNAME value does not change each time so I just delete and re-add in Cloudflare.
old --> new
https://docs.pangea.web4.world --> https://docs.tonomy.io (gitbook)
https://communication.testnet.pangea.web4.world --> https://communication.testnet.tonomy.io (digital ocean app)
for https://docs.tonomy.io/
I see
The hostname is part of a banned domain. This web property cannot be added to Cloudflare at this time. If you are an Enterprise customer, please contact your Customer Success Manager. Otherwise, please email [email protected] with the name of the web property and a detailed explanation of your association with this web property.(Gitbook, and it looks like DigitalOcean as well, use CF For SaaS/a solution by Cloudflare to hook up Custom Domains, so Cloudflare's banned domain list matters here) Do you have unpaid invoices, perhaps? Would be the easiest cause and fix
thanks. will look into this. I emailed abuserreply a few hours ago on suggestion by gitbook
just paid a $1.91 overdue bill from 19 Jan. maybe that was it!
ill wait a bit and try again
Hostname not banned or blockedlooks like it. I'm just checking by attempting to add it to my CF For SaaS setup, so it should be working now (you'll have to readd the custom domain with those partners for it to unblock)
nice. that has now worked for digital ocean. but for gitbook i am getting the same
(screenshots from gitbook)
sounds like they're not deleting/readding it fully