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

91–100 of 128 posts

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

#91

Post by madars »

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

Similar for dnscrypt-proxy: add "forwarding_rules = '/etc/dnscrypt-proxy/forwarding_rules.txt'" to /etc/dnscrypt-proxy/dnscrypt-proxy.toml and then populate the forwarding_rules.txt with lines like "archive.is 8.8.8.8".

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

#92

Post by raxi »

judge2020 wrote: post #87
raxi wrote: post #73

Earlier quoted context omitted.

Exactly on your link, just ctrl-F for "Netflix": "We are working with the small number of networks with a higher network/ISP density than Cloudflare (e.g., Netflix, Facebook, Google/YouTube) to come up with an EDNS IP Subnet alternative that gets them the information they need for geolocation". Well, I might be inaccurate in saying "exactly the same protocol as before", but it is clear that what was available to ever…

I think they mean they're working on an alternative standard, not anywhere near "we give you an API to match DNS requests to origin city". These talks might have been as simple as "we'll give you [and everyone] geoip information for the datacenters we request from based on IP, and you can load balance off that".

I do not think it has much sense if the standard is the good-old-EDNS or something new, for example supplying city name in a text form instead of hiding last bits of IP as EDNS does.

Google's 8.8.8.8 provides client-ip via EDNS to every webmaster. Zeroing at least 8 bits for privacy - it was made with privacy in mind too. The privacy could be tuned by zeroing 10+ instead of 8+ bits, etc. There is nothing wrong with EDNS and privacy, which would require to abandon ENDS with privacy stancas.

And Google provides that FOR FREE. To everyone.

How can I - as webmaster - get similar info from 1.1.1.1? Not being a Silicon Valley megacorp.

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

#93

Post by eastdakota »

raxi wrote: post #60
akerl_ wrote: post #22

Earlier quoted context omitted.

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.

No I didn’t.

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

#94

Post by eastdakota »

judge2020 wrote: post #87
raxi wrote: post #73

Earlier quoted context omitted.

Exactly on your link, just ctrl-F for "Netflix": "We are working with the small number of networks with a higher network/ISP density than Cloudflare (e.g., Netflix, Facebook, Google/YouTube) to come up with an EDNS IP Subnet alternative that gets them the information they need for geolocation". Well, I might be inaccurate in saying "exactly the same protocol as before", but it is clear that what was available to ever…

I think they mean they're working on an alternative standard, not anywhere near "we give you an API to match DNS requests to origin city". These talks might have been as simple as "we'll give you [and everyone] geoip information for the datacenters we request from based on IP, and you can load balance off that".

Exactly.

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

#95

Post by akerl_ »

raxi wrote: post #92
judge2020 wrote: post #87

Earlier quoted context omitted.

I think they mean they're working on an alternative standard, not anywhere near "we give you an API to match DNS requests to origin city". These talks might have been as simple as "we'll give you [and everyone] geoip information for the datacenters we request from based on IP, and you can load balance off that".

I do not think it has much sense if the standard is the good-old-EDNS or something new, for example supplying city name in a text form instead of hiding last bits of IP as EDNS does. Google's 8.8.8.8 provides client-ip via EDNS to every webmaster. Zeroing at least 8 bits for privacy - it was made with privacy in mind too. The privacy could be tuned by zeroing 10+ instead of 8+ bits, etc. There is nothing wrong with E…

Again, you keep presenting this as something Cloudflare provides to “megacorps” for money. There’s no evidence this is the case, it’s just your speculation.

I’m really sorry that you somehow depend heavily on EDNS Client Subnets, a feature that was only standardized 5 years ago. But it’s optional, per the spec, and Cloudflare has published their rationale for not enabling it on their resolvers.

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

#96

Post by raxi »

akerl_ wrote: post #95
raxi wrote: post #92

Earlier quoted context omitted.

I do not think it has much sense if the standard is the good-old-EDNS or something new, for example supplying city name in a text form instead of hiding last bits of IP as EDNS does. Google's 8.8.8.8 provides client-ip via EDNS to every webmaster. Zeroing at least 8 bits for privacy - it was made with privacy in mind too. The privacy could be tuned by zeroing 10+ instead of 8+ bits, etc. There is nothing wrong with E…

Again, you keep presenting this as something Cloudflare provides to “megacorps” for money. There’s no evidence this is the case, it’s just your speculation. I’m really sorry that you somehow depend heavily on EDNS Client Subnets, a feature that was only standardized 5 years ago. But it’s optional, per the spec, and Cloudflare has published their rationale for not enabling it on their resolvers.

Please, tell me - not a megacorp webmaster - how can I opt-in to Cloudflare program available to Facebook/Netflix, to get what is available freely as the source IP of UDP packet in the absence of planet-wide public resolvers and what Google gives for free trying to mitigate the inconvenience caused by the planet-wide resolver.

Indeed, my texts about possible motivation is speculations, but I do understand why webmasters block CloudFlare DNS.

I wonder why there are so few of them.

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

#97

Post by blibble »

wodenokoto wrote: post #81

There is so much I do not know about dns. I thought: I ask dns server about domain, they return an IP address. I connect to IP address and they in turn can see mine. So why does cloud flare need to a) query domain for IP address on my behalf? Can’t they just do it on their own behalf and cache the results? B) why do they need to hide my IP address information from the domain? Aren’t I going to visit the destination r…

some people use the IP from the DNS query to return a server closer to you

that's pretty much it

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

#98

Post by akerl_ »

raxi wrote: post #96
akerl_ wrote: post #95

Earlier quoted context omitted.

Again, you keep presenting this as something Cloudflare provides to “megacorps” for money. There’s no evidence this is the case, it’s just your speculation. I’m really sorry that you somehow depend heavily on EDNS Client Subnets, a feature that was only standardized 5 years ago. But it’s optional, per the spec, and Cloudflare has published their rationale for not enabling it on their resolvers.

Please, tell me - not a megacorp webmaster - how can I opt-in to Cloudflare program available to Facebook/Netflix, to get what is available freely as the source IP of UDP packet in the absence of planet-wide public resolvers and what Google gives for free trying to mitigate the inconvenience caused by the planet-wide resolver. Indeed, my texts about possible motivation is speculations, but I do understand why webmast…

“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, nobody is running their own recursive resolvers. Everybody uses either their ISP’s DNS provider or one provided by a large network entity, virtually all of which are companies. This has been the case for decades. So anybody relying on the source IP of the UDP packet is just out of luck, and has always been out of luck. It’s clear you wish this wasn’t the case, but Cloudflare and Google aren’t really changing the game here, and they don’t owe you optional features because you really want to see user IP data.

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

#99

Post by mercora »

i have no trouble to resolve www.archive.is via 1.1.1.1 at all...

however, i noticed archive.is has a CNAME record pointing to www.archive.is while CNAME RR on apex domains are usually not allowed in DNS... what make this even more interesting, i only see the CNAME RR when querying via 1.1.1.1 and not when querying authoritative servers for archive.is (EDIT: while repeating the query via 1.1.1.1 i also saw both A and CNAME record for archive.is in the response :S)

maybe the initial issue is just gone already? considering this is apparently happening in 2019 that does not seem too unlikely...

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

#100

Post by kelnos »

oenetan wrote: post #83
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?

Fair use applies i think.

I don't think retaining and publishing complete copies of copyrighted works falls under even the most generous interpretation of fair use.
Post reply on HN