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

111–120 of 128 posts

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

#111

Post by dilyevsky »

voldacar wrote: post #68

I don't fully understand how archive.is operates. They don't remove copyrighted content (which I like, since it provides a useful service), they must have probably terabytes upon terabytes of data in some datacenter somewhere, yet they never seem to be shut down by the govt or their datacenter/cloud provider. Am I just naive to be surprised by this? How does all this work exactly?

They’re in russia so dgaf about this. The insistence on tracking and absence of https when served from inside russia kind of implies all sorts of things. Use archive.org

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

#112

Post by raxi »

akerl_ wrote: post #109
raxi wrote: post #105

Earlier quoted context omitted.

I guess you just do not understand what EDNS is, and why it is optional and why its optional-ness is not a pro-CloudFlare argument. It is very simple: Query(source IP is an ISP in Paris, no EDNS): gimme IP of "website.com" WebsiteComDNS: IP of the server closest to Paris Query(source IP is Google, no-EDNS): gimme IP of "website.com" WebsiteComDNS: Hm, it is likely Google Cloud, or GoogleBot, answer with IP of own ser…

I appreciate that you’ve moved from assuming what Cloudflare is doing to assuming what I understand. I think this thread has run its course.

I concluded that from sentences like "they don’t owe you optional features because you really want to see user IP data" which reveal misunderstanding on who is sending queries and who decides what to answer to those queries.

From your text it looks like webmasters are sending requests to CloudFlare to get user's IP.

This is totally wrong.

It is CloudFlare wants to see server IP and in the query it has to explain how they will use this info, to which region they will forward my server IP.

That is what EDNS-client-IP for.

If the requester refuses to explain why they need the server IP address for (and their goal cannot be derived from the source IP of the UDP packet, like in the case of local ISP resolvers), they may be denied the privilege of the honor of receiving responses.

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

#113

Post by retox »

jbreitbart wrote: post #55
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

There are quite a few different TLDs that the site uses (for resilience I presume). .vn is another, .today may still be in use.

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

#114

Post by indianets »

I had a similar issue with VoWiFi on my network due to EDNS, and it's rightly pointed out by msilverlock in forum.

  # dig vowifi.jio.com @1.1.1.1 A
  ;; ANSWER SECTION:
  vowifi.jio.com. 5 IN A 49.45.63.1
  vowifi.jio.com. 5 IN A 49.45.63.2
  ;; SERVER: 1.1.1.1#53(1.1.1.1)

  # dig vowifi.jio.com @8.8.8.8 A
  ;; ANSWER SECTION:
  vowifi.jio.com. 4 IN A 49.44.59.36
  vowifi.jio.com. 4 IN A 49.44.59.38
  ;; SERVER: 8.8.8.8#53(8.8.8.8)
https://community.cloudflare.com/t/vowifi-issues-due-to-poss...

As the article links to and says "privacy versus convenience", and I am happy that CloudFlare chose the former.

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

#115

Post by nora-puchreiner »

indianets wrote: post #114

I had a similar issue with VoWiFi on my network due to EDNS, and it's rightly pointed out by msilverlock in forum. # dig vowifi.jio.com @1.1.1.1 A ;; ANSWER SECTION: vowifi.jio.com. 5 IN A 49.45.63.1 vowifi.jio.com. 5 IN A 49.45.63.2 ;; SERVER: 1.1.1.1#53(1.1.1.1) # dig vowifi.jio.com @8.8.8.8 A ;; ANSWER SECTION: vowifi.jio.com. 4 IN A 49.44.59.36 vowifi.jio.com. 4 IN A 49.44.59.38 ;; SERVER: 8.8.8.8#53(8.8.8.8) htt…

That million Firefox users who chose Cloudflare DNS must know that chose "privacy versus convenience" too and be happy with that.

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

#116

Post by voldacar »

dilyevsky wrote: post #111
voldacar wrote: post #68

I don't fully understand how archive.is operates. They don't remove copyrighted content (which I like, since it provides a useful service), they must have probably terabytes upon terabytes of data in some datacenter somewhere, yet they never seem to be shut down by the govt or their datacenter/cloud provider. Am I just naive to be surprised by this? How does all this work exactly?

They’re in russia so dgaf about this. The insistence on tracking and absence of https when served from inside russia kind of implies all sorts of things. Use archive.org

I will continue to use them because things get taken down from archive.org sometimes, or at any rate far more often than with archive.is. I consider it a bug when anything disappears from an archive for any reason.

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

#117

Post by grapist420 »

voldacar wrote: post #68

I don't fully understand how archive.is operates. They don't remove copyrighted content (which I like, since it provides a useful service), they must have probably terabytes upon terabytes of data in some datacenter somewhere, yet they never seem to be shut down by the govt or their datacenter/cloud provider. Am I just naive to be surprised by this? How does all this work exactly?

It’s apparently self funded by him. I don’t know how he doesn’t get shut down but I don’t know how all the DMCA avoiding pirated streaming sites don’t either, or how sci hub isn’t domain blocked in the US, or why millions of copyrighted books aren’t DMCAed from libgen.

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

#118

Post by tinus_hn »

voldacar wrote: post #68

I don't fully understand how archive.is operates. They don't remove copyrighted content (which I like, since it provides a useful service), they must have probably terabytes upon terabytes of data in some datacenter somewhere, yet they never seem to be shut down by the govt or their datacenter/cloud provider. Am I just naive to be surprised by this? How does all this work exactly?

It’s easy, you just make yourself unavailable for contact, there’s plenty of providers that don’t care what you do. It’ll take years to get banned.

The internet is global, it’s a choice to apply US law like the dmca. You can also choose not to.

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

#119

Post by tinus_hn »

urthor wrote: post #108
voldacar wrote: post #84

Earlier quoted context omitted.

Things on archive.org get DMCA'ed all the time

I'm almost certain the actual reason is producing all the infrastructure to DMCA content on Google/Facebook/Twitter/Youtube and other "mainstream" Web 2.0 platforms is expensive . Copyright enforcement is a lot stricter on Youtube, than say, Reddit video. It's all down to the engagement of the IP owners. My guess is they just haven't gotten around to chasing Archive.is down that hard.

It’s a value proposition. Archive.is doesn’t host Hollywood blockbusters. If it is hard to take them down, nobody is going to do that as long as they don’t cause to much real damage.

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

#120

Post by rb12345 »

raxi wrote: post #103
akerl_ wrote: post #98

Earlier quoted context omitted.

“We publish the geolocation information of the IPs that we query from”, from the linked comment above. They publish the same info to you and Netflix and me and Amazon. You keep presenting a difference between what “you” get and what a “megacorp” gets, without any evidence that they’re getting something different from you. You also sidestep here into a complaint against “planet wide resolvers”. To a rounding error, no…

> You keep presenting a difference between what “you” get and what a “megacorp” gets, without any evidence that they’re getting something different from you. I read it in Mattew Prince sentence above > > You also sidestep here into a complaint against “planet wide resolvers”. To a rounding error, nobody is running their own recursive resolvers. Everybody uses either their ISP’s DNS provider or one provided by a large…

Likely because DNS worked just fine without EDNS client IP (and indeed DNS) for decades. For example, I remember the use of the 4.2.2.2 server, which was globally accessible but US-based. The responses though were 100% usable wherever you were on the planet. Equally, a national ISP running DNS servers would get you a country at most; a /24 gives you city or better location, carrier-grade NAT aside. Latency between the client and server may be slightly higher, but that's the end user's problem and not an issue for the site. In any case, it sounds like the Cloudflare source IPs for recursive DNS lookups are locatable via GeoIP, so I fail to see the problem.
Post reply on HN