zlacker

>>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?

>>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.

>>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?

>>cnst+p6
> 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.

If archive.is thinks that Internet standards should be adopted so quickly, it's weird that they don't support IPv6 considering it's been a standard since 1998!

Obviously I'm kidding, but only kind of. When it comes to insisting on adopting new standards, edns-client-subnet is a weird hill to die on, especially considering it was always meant to be optional.

> does Cloudflare the CDN simply disregard ECS when receiving requests from DNS.Google, or do they take it into account?

I don't think they have a reason to use it because they use TCP anycast. Looking at https://cachecheck.opendns.com/ they seem to return the same IPs regardless of geography.