Comment by Brian_K_White
2 years ago
To fix archive.is links, switch your dns off of cloudflare.
You may be able to do it just for archive.is/ph/md/today without affecting dns for any other lookups, depending where/how you choose to edit.
In my case at home I have an opnsense router and using the unbound dns resolver to provide some lan names as well as forwarding the rest to the internet. In there it has a "domain overrides" tab where I specified another dns server just for archive.is .ph .md .today
So 99% of lookups are going to cloudflare, and just lookups for those domains are going to another dns server. And now those links work for any machine at home.
There are other ways to do the same thing different ways in different places like on your laptop or phone, or maybe even just in one browser.
For example a lot of people mistakenly think the problem is dns-over-https because truning off doh makes it work. But that's just an example of a handy way to get the result of turning cloudflare on & off, if cloudflare is only configured in the doh config and not in the normal dns config, etc.
Very interesting, and the likely culprit. Thanks!
Does cloudflare DNS block those domains?
No. It's a long annoying dickfight between the two. And the reason it's annoying is they are both right, ish.
Actually Cloudflare is solidly more right, both because of what they are doing, why, and how they are open to finding some sort of compromise, and it's Archive.is who both have the weaker case to justify what they want, and explicitly give no fucks and unwilling to bother working with the other party on any sort of solution, and also what they are doing at the technical level is just technically wrong violating specs vs what cloudflare is doing is not.
archive.is wants the users ip for geo load balancing, cloudflare does not supply the users ip for privacy. archive.is returns intentionally and artificially incorrect results to lookups that come from cloudflare.
It's been the same for years now.
I am no Cloudflare fanboi even though I am using their dns obviously. It's just how all the factors shake out as far as I can tell.
https://news.ycombinator.com/item?id=19828702
This is told by Cloudflare ceo from their side, but it is also sort of the definitive explaination of the situation. But if you google cloudflare archive.is you can find countless other discussions and explainations. Surely somewhere archive.is must have written up a version that paints themselves as righteous and blameless, but in the end I don't see how you can get around the base facts of who is doing what. The actions are how you tell the difference between the two sides.