;; ANSWER SECTION: help.leavemealone.app. 0 IN CNAME help.leavemealone.com.
help.leavemealone.com. 0 IN CNAME leavemealone.helpkit.so.
leavemealone.helpkit.so. 0 IN CNAME helpkit-ssr.onrender.com.
helpkit-ssr.onrender.com. 0 IN CNAME helpkit-ssr.onrender.com.cdn.cloudflare.net.
helpkit-ssr.onrender.com.cdn.cloudflare.net. 0 IN A 216.24.57.3
helpkit-ssr.onrender.com.cdn.cloudflare.net. 0 IN A 216.24.57.253
EDIT: This is a CNAME chain and although it's not recommended it's valid https://serverfault.com/a/309660
You can read more info here: https://community.cloudflare.com/t/dns-subdomain-no-longer-w...
Gitbook is nowhere in the chain
There's a redirect happening somewhere but it ain't from the web server listed on the DNS record.
Authorative A records:
# help.leavemealone.app
help.leavemealone.app. 60 IN CNAME help.leavemealone.com.
# help.leavemealone.com
help.leavemealone.com. 30 IN CNAME leavemealone.helpkit.so.
# leavemealone.helpkit.so
leavemealone.helpkit.so. 1799 IN CNAME helpkit-ssr.onrender.com.
# helpkit-ssr.onrender.com
helpkit-ssr.onrender.com. 300 IN CNAME helpkit-ssr.onrender.com.cdn.cloudflare.net.
# Authorative A records for helpkit-ssr.onrender.com.cdn.cloudflare.net:
helpkit-ssr.onrender.com.cdn.cloudflare.net. 300 IN A 216.24.57.3 helpkit-ssr.onrender.com.cdn.cloudflare.net. 300 IN A 216.24.57.253
--
Indeed opening the page loads 216.24.57.3 where I get a HTTPS response with statusCode 302 that redirects to -> https://dinkydani.gitbook.io/leave-me-alone-help/
Seems to be what should happen?
ps - I'm stunned though to see 4 CNAMEs, especially with 60 and 30s TTLs
I had changed the CNAME pointing to GitBook to my new service, and dig etc was reporting that it had propagated correctly. BUT the URL was still resolving to GitBook.
I was pulling my hair out and questioning my entire understanding of how DNS works.
From what I can tell Cloudflare "partners" can introduce redirect rules that are prioritized over our own Cloudflare DNS rules. This sounds completely insane to me, there's no way SaaS providers should be able to hijack control of DNS like this.