Tell HN: Archive.is inaccessible via Cloudflare DNS (1.1.1.1)

Re:Tell HN: Archive.is inaccessible via Cloudflare DNS (1.1.... by jasonhansel on Saturday May 04, 2019 @04:49PM (#19829291)

Also: it'd be nice if CloudFlare made a secondary DNS resolver (1.1.2.2?) that didn't pass along EDNS information, as a backup for websites like archive.is (and for anyone who cares about privacy).

[ Parent | on HN ]

Re:Tell HN: Archive.is inaccessible via Cloudflare DNS (1.1.... by akerl_ on Saturday May 04, 2019 @06:16PM (#19829737)

I think you may have typo’d, but just in case:

1.1.1.1 does not send EDNS ECS data, specifically because of the privacy concern. So the hypothetical secondary resolver would need to send that data, for people who aren’t concerned about the privacy implications / want to get to archive.is.

Given CloudFlare’s stated message of prioritizing privacy, it seems unlikely they’d stand up infrastructure that behaved like 1.1.1.1 except that it leaked more private information.

[ Parent | on HN ]

Re:Tell HN: Archive.is inaccessible via Cloudflare DNS (1.1.... by jasonhansel on Saturday May 04, 2019 @09:53PM (#19830619)

My apologies! I misread the OP and thought that CloudFlare was being accused of violating privacy. Instead, it seems that CloudFlare is definitely making the right choice, and I can't see why archive.is has any objection.

[ Parent | on HN ]

Re:Tell HN: Archive.is inaccessible via Cloudflare DNS (1.1.... by jasonhansel on Sunday May 05, 2019 @11:00AM (#19833130)

(Also: I only just learned that archive.is != archive.org.)

[ Parent | on HN ]