3 ms·
If you are using Cloudflare for DNS you will run into that issue. It is by design. https://community.cloudflare.com/t/archive-today-does-not-resolve-with-1-1-1
by willk 3y ago
If you are using Cloudflare for DNS you will run into that issue. It is by design.
https://community.cloudflare.com/t/archive-today-does-not-resolve-with-1-1-1-1-works-fine-on-other-resolvers/71315 https://community.cloudflare.com/t/archive-today-does-not-re...
- jzl 3y agoAhh wow, thanks. Indeed, I do use 1.1.1.1.
- tsimionescu 3y agoDon't worry, it almost certainly has nothing to do with that (though there is plenty to complain about with 1.1.1.1).
- sph 3y agoNot the same issue, though it is still because of Cloudflare's shenanigans. One affects their DNS resolution of archive.is, GP is talking about Cloudflare's endless captcha portal on that site. Strangely enough, it works for me today, but a few days ago I couldn't get past that obnoxious screen. I just wish people would stop flocking to Cloudflare and making the internet even shittier than it is.
- iainmerrick 3y agoCan you go into a bit more detail about this? The thread you’ve linked to isn’t very clear on its own -- it seems like it’s missing a lot of context. The first reply makes it sound like archive.is is blocking Cloudflare, but it sounded like you meant the opposite. (And I assume this is all separate from the CAPTCHA thing, as the other reply says)