Re:GitBook bypassing Cloudflare DNS to route traffic to thei...
by SamyPesse on Wednesday November 23, 2022 @04:15AM
(#33716885)
We only remove the domain from Cloudflare when the content is deleted. The main reason is to avoid broken links when users update their domain on GitBook.
Ex:
1. You configure docs.mycompany.com with your GitBook space
2. You share links to docs.mycompany.com on social medias
3. You update the domain to docs.anothercompany.com
4. It's better if the docs.mycompany.com links can continue working until you remove the DNS entry
In summary, we want the users to decide through their DNS config when GitBook should serve the content or not to avoid breaking links without an intentional action from the user.
Unfortunately, because of how Cloudflare doesn't use the DNS configuration to decide where to route the traffic, it causes issues atm. We'll look at what we can do on our side to mitigate this.
Ex: 1. You configure docs.mycompany.com with your GitBook space 2. You share links to docs.mycompany.com on social medias 3. You update the domain to docs.anothercompany.com 4. It's better if the docs.mycompany.com links can continue working until you remove the DNS entry
In summary, we want the users to decide through their DNS config when GitBook should serve the content or not to avoid breaking links without an intentional action from the user.
Unfortunately, because of how Cloudflare doesn't use the DNS configuration to decide where to route the traffic, it causes issues atm. We'll look at what we can do on our side to mitigate this.