zlacker

[return to "Why does 1.1.1.1 not resolve archive.is?"]
1. jchw+64[view] [source] 2019-10-04 06:29:19
>>stargr+(OP)
I am no expert by any means. However, I strongly suspect EDNS is not actually needed to run a CDN. There’s a lot of approaches to balancing load and distributing traffic. An example of another approach would be using anycast IPs.

I’m also surprised that traffic from Cloudflare DNS users caused any significant problem. Was it really that much traffic?

◧◩
2. profmo+F4[view] [source] 2019-10-04 06:36:27
>>jchw+64
> However, I strongly suspect EDNS is not actually needed to run a CDN.

It's not. The proof is that CDNs existed long before edns-client-subnet was introduced. All it does is allow the CDN's DNS servers to return the most optimal A/AAAA records for the client. But the worst that should happen without it is you get sent to a more distant CDN server, and the content loads more slowly.

The fact that archive.is somehow suffers without this feature (which, btw, wasn't standardized until 2016) suggests they're doing something really, really odd. If I were them, I'd focus on making my system more robust, rather than demanding the rest of the Internet adopt a relatively young, optional DNS extension.

◧◩◪
3. cnst+p6[view] [source] 2019-10-04 07:02:11
>>profmo+F4
Per https://serverfault.com/a/560059/110020, Google's 8.8.8.8 has had support for `edns0-client-subnet` since at least 2013, so, even if it's only been standardised in 2016, it's been a de-factor standard for quite a while, especially in the internet-technology-years.

Here's an interesting thought — if it's so bad for privacy and isn't necessary for a CDN, does Cloudflare the CDN simply disregard ECS when receiving requests from DNS.Google, or do they take it into account?

◧◩◪◨
4. darkla+08[view] [source] 2019-10-04 07:26:12
>>cnst+p6
> if it's so bad for privacy and isn't necessary for a CDN, does Cloudflare the CDN simply disregard ECS when receiving requests from DNS.Google, or do they take it into account?

I don't understand that for various reasons.

1) Privacy is already lost here. If I shout my mobile number on a train with you that's full of people, everyone knows my phone number. If you choose to keep it / use it to call me tomorrow doesn't matter.

2) If Cloudflare can make _better_ decisions based on the information shared by Google, why shouldn't they? As long as it is optional and they don't take their ball and go home^W^W^W^W^W^Wreply with 127.0.0.3 in cases where you don't provide it..

[go to top]