GitBook bypassing Cloudflare DNS to route traffic to their domain

Re:GitBook bypassing Cloudflare DNS to route traffic to thei... by jivings on Wednesday November 23, 2022 @02:22AM (#33716194)

The A records that you've gotten to are unrelated to Gitbook and there are no 302 redirects on our side. As far as I understand it's some internal redirect happening in Cloudflare's network.

You can read more info here: https://community.cloudflare.com/t/dns-subdomain-no-longer-w...

[ Parent | on HN ]

Re:GitBook bypassing Cloudflare DNS to route traffic to thei... by bauruine on Wednesday November 23, 2022 @03:03AM (#33716431)

Thanks for the explanation. I still don't know exactly what's going on here. How do the DNS records look on the Cloudflare UI?

[ Parent | on HN ]

Re:GitBook bypassing Cloudflare DNS to route traffic to thei... by jivings on Wednesday November 23, 2022 @03:54AM (#33716729)

help.leavemealone.app -> CNAME -> help.leavemealone.com -> CNAME -> leavemealone.helpkit.so

Gitbook is nowhere in the chain

[ Parent | on HN ]

Re:GitBook bypassing Cloudflare DNS to route traffic to thei... by bauruine on Wednesday November 23, 2022 @04:04AM (#33716798)

Then you have to ask helpkit.so why they are using render.com to do the redirect.

[ Parent | on HN ]

Re:GitBook bypassing Cloudflare DNS to route traffic to thei... by bauruine on Wednesday November 23, 2022 @04:29AM (#33716981)

But it's hitting their DNS zone and they have decided to add a CNAME to helpkit-ssr.onrender.com for leavemealone.helpkit.so.

[ Parent | on HN ]

Re:GitBook bypassing Cloudflare DNS to route traffic to thei... by jivings on Wednesday November 23, 2022 @04:24AM (#33716939)

The request is never hitting HelpKit's servers.

[ Parent | on HN ]