After leaving Gitbook, they can’t get control of their subdomains back, even after adding their own CNAME or A records for the subdomain. Because they delete the Gitbook site, this generally results in 404.
It seems that Gitbook also uses Cloudflare and may be some sort of Cloudflare partner. It seems that Gitbook is not updating its records and/or not giving back control of traffic for the subdomains that were routed to it.
(Yes, they’ve waited 24 hours, purged the cache etc.)
The reason I’ve gone down this rabbit hole is that, unfortunately, I can also reproduce it.
Most users would say this just shouldn’t be possible. Domain on Cloudflare, DNS on Cloudflare, pointing to your own website, and yet traffic is going to a 3rd party.
Cloudflare partners like Gitbook should have more restricted power.
Cloudflare partners like Gitbook should with power should be forced to use it more responsibly, specifically on cleanup (when a client leaves).
Does this happen with other Cloudflare partners?
Is there already a way to force a reset from the Cloudflare side?