My issue is very similar to the one posted here. In short, we initially enabled our documentation website using Gitbook[dot]com, but when we stumbled upon a few issues, we decided to move to Read The Docs (readthedocs[dot]org) (RTD).
Things quickly started to get funky, because as much as I added the
docs CNAME entry to
readthedocs.io, it would still continue to redirect to a Gitbook error. The RTD staff was kind enough to let me know that their servers were never hit, despite this DNS entry being clearly declared in our DNS zone. Yes, I checked the page rules and I indeed even enabled development mode.
After creating ticket #2077708 (suggested as the “go-to” strategy by the linked post), the subdomain
docs.hoprnet.org now shows a
DNS_PROBE_FINISHED_NXDOMAIN error, despite being clearly defined in our DNS zone. The oddest thing is that the entry
docs in our zone does not show the usual proxy on/off orange/gray cloud, usually reserved to wildcard entries, as described in your documentation.
At this point, we are at loss on the best way to go. Gitbook announced last year they were moving to Cloudflare after an issue with Google domains, which I imagine might have led to the source of our particular error, yet does not help us to recover a stable state for the
Right now, I’ve enabled a page rule to redirect to our RTD link at hoprnet[dot]readthedocs[dot]io/en/latest/, and a What’s My DNS still points to the RTD CNAME, but docs[dot]hoprnet[dot]org still shows a
DNS_PROBE_FINISHED_NXDOMAIN error. Running
curl -IL https://docs.hoprnet.org simply does not resolve the query, which it used to return a bunch of Gitbook headers in the past.