zlacker

[return to "Does Cloudflare’s 1.1.1.1 DNS Block Archive.is? (2019)"]
1. wkat42+s8[view] [source] 2023-08-02 14:17:12
>>lolind+(OP)
Maybe they need it to route the traffic to the right CDN? That kinda would make sense.

While I'm very privacy conscious, I don't really see the benefit to hiding my region in the DNS request. Because the very next step after the DNS is my browser making a request to their webserver, at which time they will have my actual complete IP anyway.

◧◩
2. philwe+p9[view] [source] 2023-08-02 14:21:33
>>wkat42+s8
This is actually addressed in the original HN comment the post links to (>>19828702 ):

> EDNS IP subsets can be used to better geolocate responses for services that use DNS-based load balancing. However, 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.

◧◩◪
3. wkat42+ld[view] [source] 2023-08-02 14:37:58
>>philwe+p9
Yeah but if the site standardized on EDNS to get this information, it's rather difficult to do something different just for Cloudflare.
◧◩◪◨
4. p1mrx+jg[view] [source] 2023-08-02 14:51:57
>>wkat42+ld
edns-client-subnet only provides an IP address; the receiving CDN still needs to geolocate it.

So the main difference is that Cloudflare's servers need to be present in the IP geolocation database. Given their prevalence, they're probably in most of them already.

[go to top]