4 ms·

This happens if you use 1.1.1.1 as your DNS resolver, the result of a long-running dispute between Cloudflare and Archive.is[1]; searching HN for “archive cloud

This happens if you use 1.1.1.1 as your DNS resolver, the result of a long-running dispute between Cloudflare and Archive.is[1]; searching HN for “archive cloudflare” will get you lots of discussion. As I understand it: the technical cause is that the Archive.is authoritative DNS server refuses to respond correctly to requests without EDNS subnet information, and Cloudflare’s resolver refuses to send requests with it. (Cloudflare says this is for privacy reasons, and I believe Archive.is says their response is for legal reasons.) The captcha loop seems to be a recent development; apparently[2] it’s not actually from Cloudflare, just styled to look like it. [1] https://jarv.is/notes/cloudflare-dns-archive-is-blocked/ https://jarv.is/notes/cloudflare-dns-archive-is-blocked/ [2] https://news.ycombinator.com/item?id=38174302 https://news.ycombinator.com/item?id=38174302

kmeisthax 3y ago
Sooooo the weird thing for me is that I never actually used 1.1.1.1, and it's not in my DNS. archive.today loads correctly in Chrome without a problem so I suspect Firefox is just using 1.1.1.1 over DoH or something.
- toomuchtodo 3y ago
  Appears so. https://developers.cloudflare.com/1.1.1.1/privacy/cloudflare-resolver-firefox/ https://developers.cloudflare.com/1.1.1.1/privacy/cloudflare... > To counter such threats, Mozilla has partnered with Cloudflare to provide direct DNS resolution from within the Firefox browser using the Cloudflare Resolver for Firefox. What this means is that whenever you select or type a web address in the Firefox browser your DNS lookup request will be sent over a secure channel to the Cloudflare Resolver for Firefox rather than to an unknown DNS resolver, significantly decreasing the odds of any unwanted spying or man in the middle attacks.
- lazycouchpotato 3y ago
  That might just be the case. You can try switching to NextDNS within Firefox's settings.
jasonwatkinspdx 3y ago
I've been getting the same behavior while using google DNS (8.8.8.8). Is this the same dispute somehow?

kmeisthax 3y ago

Sooooo the weird thing for me is that I never actually used 1.1.1.1, and it's not in my DNS. archive.today loads correctly in Chrome without a problem so I suspect Firefox is just using 1.1.1.1 over DoH or something.

toomuchtodo 3y ago
Appears so. https://developers.cloudflare.com/1.1.1.1/privacy/cloudflare-resolver-firefox/ https://developers.cloudflare.com/1.1.1.1/privacy/cloudflare... > To counter such threats, Mozilla has partnered with Cloudflare to provide direct DNS resolution from within the Firefox browser using the Cloudflare Resolver for Firefox. What this means is that whenever you select or type a web address in the Firefox browser your DNS lookup request will be sent over a secure channel to the Cloudflare Resolver for Firefox rather than to an unknown DNS resolver, significantly decreasing the odds of any unwanted spying or man in the middle attacks.
lazycouchpotato 3y ago
That might just be the case. You can try switching to NextDNS within Firefox's settings.

jasonwatkinspdx 3y ago

I've been getting the same behavior while using google DNS (8.8.8.8). Is this the same dispute somehow?