Archive.* sabotages their DNS records when Cloudflare queries for them. They don't like that Cloudflare doesn't do EDNS forwarding so they broke their service for people using 1.1.1.1.
That said, I have the same problem. Even hard coding the IP address I resolved through Google doesn't seem to work. I'm guessing their sabotage may have backfired and is causing issues beyond their intentional scope?
if you can't trust your isp than either find someone that you can trust (by verification) or run your own resolver.
there was a recent move from the eu to have an eu-centric public resolver which brought up the question if/how the big players address country specific filtering requirements which in turn might have shed some light on the fact that gog/cf didn't care; until now.
ttctciyf|2 years ago
DNS was ISP, not 1.1.1.1, and I get the same behaviour after switching to 8.8.8.8.
jeroenhd|2 years ago
That said, I have the same problem. Even hard coding the IP address I resolved through Google doesn't seem to work. I'm guessing their sabotage may have backfired and is causing issues beyond their intentional scope?
Trouble_007|2 years ago
captcha is CF
Related: Does Cloudflare’s 1.1.1.1 DNS Block Archive.is? (2019)
HN Discussion (209-comments 2023-08-02) https://news.ycombinator.com/item?id=36970702
I just snapshot this page for a test : https://archive.is/MUhAP = https://news.ycombinator.com/item?id=37009598
Edit of formatting for readability.
dredmorbius|2 years ago
Do they run their own resolver, or rely on an extant service?
stonogo|2 years ago
abwizz|2 years ago
there was a recent move from the eu to have an eu-centric public resolver which brought up the question if/how the big players address country specific filtering requirements which in turn might have shed some light on the fact that gog/cf didn't care; until now.