Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Does Cloudflare's 1.1.1.1 DNS Block Archive.is? (2019)

jarv.is

Post reply on HN
Print view View original

51–60 of 128 posts

Re: Does Cloudflare's 1.1.1.1 DNS Block Archive.is? (2019)

#51

Post by oenetan »

Jerry2 wrote: post #47
oenetan wrote: post #31

Earlier quoted context omitted.

Everything on archive.is is on archive.org. I would say 99% of stuff. If archive.is goes down we have webcitation.org, etched.page, ghostarchive.org, webrecorder.net, etc....

> Everything on archive.is is on archive.org. I would say 99% of stuff. Given how a LOT of the stuff today is behind paywalls and Archive.today breaks through most of them and Archive.org doesn't, your "99%" figure is way, way off when it comes to popular stuff. Anyway, I donate to both the Archive.today and Archive.org. They're extremely valuable to me. I feel like Archive.today is in a dire situation when it comes…

I should have said 99% of stuff that is at risk of being lost forever. Paywalled content from major news companies isn't going anywhere anytime soon.

Re: Does Cloudflare's 1.1.1.1 DNS Block Archive.is? (2019)

#52

Post by metalliqaz »

fragmede wrote: post #34
luckylion wrote: post #15

Earlier quoted context omitted.

Can we not call literally everything "anticompetitive"? archive.is isn't a competitor of Cloudflare. Cloudflare doesn't treat them differently from any other site, they're not doing anything "to keep them down", their DNS product just has a focus that isn't compatible with archive.is' hunger for data. That you might connect to archive.is directly isn't of any concern. You might also not do that, and they've decided t…

> Cloudflare doesn't treat them differently from any other site Did we read the same article? Cloudflare is treating them, and anybody else that makes the same choices wrt EDNS, differently from the rest of the Internet.

I read the article, I'm pretty sure you are mistaken.

Re: Does Cloudflare's 1.1.1.1 DNS Block Archive.is? (2019)

#53

Post by jbreitbart »

In case you use pihole and want to use cloudflare for everything, but archive.is you can create the following file

cat /etc/dnsmasq.d/02-archive.is.conf server=/archive.is/8.8.8.8 server=/archive.is/8.8.4.4 server=/archive.li/8.8.8.8 server=/archive.li/8.8.4.4 server=/archive.to/8.8.8.8 server=/archive.to/8.8.4.4

Re: Does Cloudflare's 1.1.1.1 DNS Block Archive.is? (2019)

#54

Post by judge2020 »

Cthulhu_ wrote: post #10
deadalus wrote: post #4

Archive.is is unironically one of the most important websites in the world. I hope this mess gets fixed but I am not holding my breath because we are in the same position for years now. Interesting read on the probable owner of the site : https://webapps.stackexchange.com/a/149405

That reads a lot like doxxing; if someone isn't open about their identity, they don't want it out, and doing sleuthing work like this (or linking to it) can be considered doxxing. If archive.is hosts content that has been removed due to oppressive regimes' policies (including western ones), exposing their identity may put them at risk.

I think the question asked on SE "On which country are the creators and servers of archive.today / archive.is based?" incurs not a 'who is he', but 'should I trust them based on their national allegiance'. A similar idea could be presented of large Twitter misinformation accounts that have influenced the 2016-2020 (and future) elections - they're not open about their identity, but the actions they're doing most people would disagree with, so most would decide that it is morally justifiable to go digging for clues to find the source of the misinformation.

For archive.is, it's lower-stakes, but you might not be able to trust the site as an authoritative source in $x years should (for example) their home government take it over and strategically modify archives for their own purposes.

Re: Does Cloudflare's 1.1.1.1 DNS Block Archive.is? (2019)

#55

Post by jbreitbart »

jbreitbart wrote: post #53

In case you use pihole and want to use cloudflare for everything, but archive.is you can create the following file cat /etc/dnsmasq.d/02-archive.is.conf server=/archive.is/8.8.8.8 server=/archive.is/8.8.4.4 server=/archive.li/8.8.8.8 server=/archive.li/8.8.4.4 server=/archive.to/8.8.8.8 server=/archive.to/8.8.4.4

Fixed formating, sorry.

   cat -p /etc/dnsmasq.d/02-archive.is.conf
  server=/archive.is/8.8.8.8
  server=/archive.is/8.8.4.4
  server=/archive.li/8.8.8.8
  server=/archive.li/8.8.4.4
  server=/archive.to/8.8.8.8
  server=/archive.to/8.8.4.4

Re: Does Cloudflare's 1.1.1.1 DNS Block Archive.is? (2019)

#56

Post by _2d30 »

jbreitbart wrote: post #53

In case you use pihole and want to use cloudflare for everything, but archive.is you can create the following file cat /etc/dnsmasq.d/02-archive.is.conf server=/archive.is/8.8.8.8 server=/archive.is/8.8.4.4 server=/archive.li/8.8.8.8 server=/archive.li/8.8.4.4 server=/archive.to/8.8.8.8 server=/archive.to/8.8.4.4

I never even thought of configuring my pihole to allow this. Thanks! Much appreciated!!

Re: Does Cloudflare's 1.1.1.1 DNS Block Archive.is? (2019)

#57

Post by raxi »

Dylan16807 wrote: post #32

> I wrote the following reply to Matthew, praising his team's focus on the big picture Okay great, but: > 1.1.1.1 is delivered across Cloudflare’s entire network that today spans 180 cities. We publish the geolocation information of the IPs that we query from. That allows any network with less density than we have to properly return DNS-targeted results. > massive mismatch (not only on AS/Country, but even on the con…

>> 1.1.1.1 is delivered across Cloudflare’s entire network that today spans 180 cities. We publish the geolocation information of the IPs that we query from. That allows any network with less density than we have to properly return DNS-targeted results.

Cloudflare makes an exception to this rule for Archive.{today,is,...} domains. All requests for this domains come from Amazon EC2 in the U.S., not the 180 edges of Cloudflare. This was on blog.archive.today. Why? Who knows. But the decision to break up is made by both parties, not just the archive.

Source https://blog.archive.today/post/623568857709395968/i-from-th...

Re: Does Cloudflare's 1.1.1.1 DNS Block Archive.is? (2019)

#58

Post by Hamuko »

saurik wrote: post #49
judge2020 wrote: post #33

Earlier quoted context omitted.

Archive.is uses ECS (edns client subnet, which sends the client IP's /24 to the authoritative resolver) for geo-based load balancing. The problem is that all IPs in a /24 are highly likely to belong to the same city for residential connections, so plugging it into a geoip service is likely to show the actual city & state that a request originates from (the entire point of ECS). https://twitter.com/archiveis/status/10…

But when the user goes to use the IP address they got back, even more detailed information is going to be given to the endpoint; I can see this maybe being a benefit for TXT records or something? Hiding ECS from DNS queries seems to mostly just further create imbalances between companies that can afford routing at the IP level over companies that want to do cheaper routing at the DNS level. (And like, if you attempt…

You can still do routing at DNS-level as long as you have a less dense infrastructure than Cloudflare.

>1.1.1.1 is delivered across Cloudflare’s entire network that today spans 180 cities. We publish the geolocation information of the IPs that we query from. That allows any network with less density than we have to properly return DNS-targeted results.

Re: Does Cloudflare's 1.1.1.1 DNS Block Archive.is? (2019)

#59

Post by KarlKemp »

Cthulhu_ wrote: post #10
deadalus wrote: post #4

Archive.is is unironically one of the most important websites in the world. I hope this mess gets fixed but I am not holding my breath because we are in the same position for years now. Interesting read on the probable owner of the site : https://webapps.stackexchange.com/a/149405

That reads a lot like doxxing; if someone isn't open about their identity, they don't want it out, and doing sleuthing work like this (or linking to it) can be considered doxxing. If archive.is hosts content that has been removed due to oppressive regimes' policies (including western ones), exposing their identity may put them at risk.

The operator of archive.is is circumventing copyright law in close to every country on earth, including all the democratic ones. Its unique selling point is that they do not comply with site owners' requests not to archive content or to delete content archived in the past.

While that doesn't exclude them from the protection of law, my conviction is slightly weaker when it comes to arbitrary standards of behaviour people on reddit invented. How many pages to they happily serve that contain private information long deleted from the actual websites? When they mutter under their breath, "information wants to be free" (as they are want to be, at least how I imagine it), does their definition of information include their identity?

(I'm slightly irritated by the "research" in that post, though... I really don't need Wikipedia to believe that -vich is a jewish name. And jewish names of Ukrainian/Russian origin are certainly not specific to that location today. I bet there are more people with that last name in Florida than in all of Eastern Europe combined)

Re: Does Cloudflare's 1.1.1.1 DNS Block Archive.is? (2019)

#60

Post by raxi »

akerl_ wrote: post #22
dimensi0nal wrote: post #12

amazing how cloudflare has framed this anticompetitve move as a privacy thing. it doesn't matter if your dns resolver leaks part of your ip address to archive.is's dns servers when you're about to connect to archive.is from your ip address anyway. the only thing dropping the edns client subnet does is prevent services you use from giving you a server that's closer to you when you do the dns lookup. this performance i…

Just so we’re on the same page: Cloudflare decided globally not to include client IP in the EDNS data. Then archive.is decided to block Cloudflare’s resolvers from getting accurate records for their site. To circumvent this, Cloudflare would have to reverse their global stance or make a special exception to satisfy archive.is. It’s unclear how we could draw “anticompetitive” from this.

Cloudflare (Matthew Prince personally, here on Hacker News few months ago) said that they do reverse that their global stance for Netflix and some other megacorps.

So this is a super-premium feature unavailable to small players.

CloudFlare just changed how DNS behaved and charge corps to make it work as it worked before CloudFlare entered the stage.

Post reply on HN