this post was submitted on 07 Dec 2023
32 points (94.4% liked)

Technology

72784 readers
3807 users here now

This is a most excellent place for technology news and articles.


Our Rules


  1. Follow the lemmy.world rules.
  2. Only tech related news or articles.
  3. Be excellent to each other!
  4. Mod approved content bots can post up to 10 articles per day.
  5. Threads asking for personal tech support may be deleted.
  6. Politics threads may be removed.
  7. No memes allowed as posts, OK to post as comments.
  8. Only approved bots from the list below, this includes using AI responses and summaries. To ask if your bot can be added please contact a mod.
  9. Check for duplicates before posting, duplicates may be removed
  10. Accounts 7 days and younger will have their posts automatically removed.

Approved Bots


founded 2 years ago
MODERATORS
 

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?

top 11 comments
sorted by: hot top controversial new old
[–] NonDollarCurrency@monero.town 6 points 2 years ago (1 children)

Yes it's been like that forever. Before it used to outright block the entire domain.

[–] _s10e@feddit.de 1 points 2 years ago (1 children)

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 6 points 2 years ago (2 children)

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.

[–] _edge@discuss.tchncs.de 2 points 2 years ago (1 children)

Weird, I change from dns11.quad9.net (with ECS / EDNS client subnet enabled) to dns.quad9.net. Now archive.today works.

[–] _edge@discuss.tchncs.de 1 points 2 years ago (1 children)

And then it broke again. And then it worked again.

Totally random. How does one debug this?

[–] redcalcium@lemmy.institute 3 points 2 years ago (1 children)

Maybe just hard code the DNS value for archive.is in your host file or your pihole (if you use pihole)?

[–] _edge@discuss.tchncs.de 1 points 2 years ago (1 children)

Sounds like a simple solution.

Although I'm not really sure what happens here. I do get an IP address via quad9 and I do get other IP adresses using other resolvers, but how do I know which one works.

[–] redcalcium@lemmy.institute 1 points 2 years ago (1 children)

Both should work, archive.today is using a dns-based load balancer where it answer DNS query with an IP address for a server that supposedly closer to you. Just pick one with the shortest ping and see if it'll work.

[–] _edge@discuss.tchncs.de 1 points 2 years ago

But, then, why does it not work when using quad9? The result from quad9 may not be the closest server, but they can serve the captcha, so I'm reaching one of their servers.

[–] LWD@lemm.ee 1 points 2 years ago* (last edited 2 years ago)
[–] forbiddenlake@lemmy.world 4 points 2 years ago

Yes. 2019 comment from cloudflare: https://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.