this post was submitted on 30 Aug 2023
256 points (100.0% liked)

Technology

37724 readers
500 users here now

A nice place to discuss rumors, happenings, innovations, and challenges in the technology sphere. We also welcome discussions on the intersections of technology and society. If it’s technological news or discussion of technology, it probably belongs here.

Remember the overriding ethos on Beehaw: Be(e) Nice. Each user you encounter here is a person, and should be treated with kindness (even if they’re wrong, or use a Linux distro you don’t like). Personal attacks will not be tolerated.

Subcommunities on Beehaw:

This community's icon was made by Aaron Schneider, under the CC-BY-NC-SA 4.0 license.

founded 2 years ago
MODERATORS
alyaza@beehaw.org
TheRtRevKaiser@beehaw.org
gyrfalcon@beehaw.org
rs5th@beehaw.org
coldredlight@beehaw.org
Los@beehaw.org
SemioticStandard@beehaw.org
TheRtRevKaiser@kbin.social
remington@beehaw.org
256
Does Cloudflare's 1.1.1.1 DNS Block Archive.is? (jarv.is)
submitted 1 year ago by dingus@lemmy.ml to c/technology@beehaw.org
77 comments fedilink hide all child comments
 

tl;dr: No. Quite the opposite, actually — Archive.is’s owner is intentionally blocking 1.1.1.1 users.

CloudFlare's CEO had this to say on HackerNews:

We don’t block archive.is or any other domain via 1.1.1.1. [...] Archive.is’s authoritative DNS servers return bad results to 1.1.1.1 when we query them. I’ve proposed we just fix it on our end but our team, quite rightly, said that too would violate the integrity of DNS and the privacy and security promises we made to our users when we launched the service. [...] The archive.is owner has explained that he returns bad results to us because we don’t pass along the EDNS subnet information. This information leaks information about a requester’s IP and, in turn, sacrifices the privacy of users.

I am mainly making this post so that admins/moderators at BeeHaw will consider using archive.org or ghostarchive.org links instead of archive.today links.

Because anyone using CloudFlare's DNS for privacy is being denied access to archive.today links.

https://ghostarchive.org/archive/PmSkp

you are viewing a single comment's thread
view the rest of the comments
[–] metaStatic@kbin.social 4 points 1 year ago (4 children)

what else is on your list?

[–] dingus@lemmy.ml 14 points 1 year ago* (last edited 1 year ago) (2 children)
[–] Psythik@lemm.ee 2 points 1 year ago (1 children)

Do they have servers in the US?

[–] dingus@lemmy.ml 2 points 1 year ago* (last edited 1 year ago) (1 children)
[–] Psythik@lemm.ee 2 points 1 year ago

Sweet. Just changed my servers now.

[–] PeachMan@lemmy.one 6 points 1 year ago (3 children)

I do CloudFlare first and Google as backup.

[–] red@feddit.de 22 points 1 year ago

So privacy first first and privacy last second, interesting combo

[–] Bishma@discuss.tchncs.de 7 points 1 year ago

yeah 1.1.1.1 then 8.8.8.8

[–] PeachMan@lemmy.one 5 points 1 year ago

LOL that's not a bad way of explaining it. My reasoning is that I like CloudFlare, so I'll default to them, but if CF goes down I want DNS to continue working. I figure Google is one of the servers that's LEAST likely to go down.

[–] user224@lemmy.sdf.org 2 points 1 year ago

I used to use Cloudflare and recently switched to NextDNS for more control.