Submitted 11 months ago by _edge@discuss.tchncs.de to technology@lemmy.world
Today, I enabled quad9 dns for my home network, and archive.today now requires a captcha, which results in an infinite loop.
A similar problem was reported some months ago for Cloudflare’s 1.1.1.1
Posting here to see whether it’s just me or everyone. Is this a know problem?
Yes. 2019 comment from cloudflare: news.ycombinator.com/item?id=19828702
On my network, I send dns requests for only the archive domains to a DNS server that archive likes. Adguards, in this case. Everything else goes to cloudflare. Both adguardhome and unbound can do that.
NonDollarCurrency@monero.town 11 months ago
Yes it’s been like that forever. Before it used to outright block the entire domain.
_s10e@feddit.de 11 months ago
Who’s blocking what?
Last time, IIRC someone blamed Cloudflare and they said they did not do anything, just relaying from upstream.
redcalcium@lemmy.institute 11 months ago
The gist is, archive.today configured their DNS server to use edns client subnet to determine the visitor’s general location to direct them to servers closest to their area for load balancing purpose. Cloudflare DNS however doesn’t pass that information for privacy reason. I guess this piss archive.today’s dev off because their dns-based load balancing is no longer work effectively for cloudflare DNS users, so they outright block it.