3 ms·

I can hear the product managers at cloudflare maniacally laughing their heads off right now. A side-effect if you're being generous, or primary motive if you'r

I can hear the product managers at cloudflare maniacally laughing their heads off right now. A side-effect if you're being generous, or primary motive if you're being cynical, of 1.1.1.1 is that CF acquires all the geo info at the expense of everyone else. This puts CF in a particularly advantageous position over DIY GSLB (pushing content providers into using CF), as well as other CDNs of course. Not only that, the privacy policy promises they will not share resolver data with any other party! lol of course they won't -- why would they give up this competitive advantage! It means they are guaranteeing they will not pass on RFC7871 ECS info. Of course DNS-based geo isn't perfect, and there are other solutions (js pixel timing, anycast, others) but using DNS is still pretty major. Combining it with anycast, as CF does, is surely powerful. Getting FF to use 1.1.1.1 so that "user's don't have to" is incredible. Someone at CF is getting a huge bonus this year.

r-w 8y ago
Please do your research. “Any data Cloudflare handles as a result of its resolver for Firefox is as a date processor acting pursuant to Firefox’s data processing instructions. Therefore, the data Cloudflare collects and processes pursuant to its agreement with Firefox is not covered by the Cloudflare Privacy Policy. As part of its agreement with Firefox, Cloudflare has agreed to collect only a limited amount of data about the DNS requests that are sent to the Cloudflare Resolver for Firefox via the Firefox browser. Cloudflare will collect only the following information from Firefox users: […] All of the above information will be stored briefly as part of Cloudflare’s temporary logs, and then permanently deleted within 24 hours of Cloudflare’s receipt of such information.” source: https://developers.cloudflare.com/1.1.1.1/commitment-to-privacy/privacy-policy/firefox/ https://developers.cloudflare.com/1.1.1.1/commitment-to-priv...
- bluejekyll 8y ago
  > ... DNS requests that are sent to the Cloudflare Resolver for Firefox via the Firefox browser. Is this Firefox specific (via HTTP headers or EDNS options) or is this just the general policy of the 1.1.1.1 resolver for all users?
  - sp332 8y ago
    The original article says they're not using CloudFlare's normal DNS-over-HTTPS endpoint, so this is probably specific to Firefox. Edit: according to https://www.cloudflare.com/privacypolicy/ https://www.cloudflare.com/privacypolicy/ the normal privacy policy applies to users of CloudFlare's DNS.
zackbloom 8y ago
The reason we (Cloudflare) don't share ECS info is to protect the privacy of the querying user by not exposing their full IP address to the authoritative resolver. We are exploring ways we can pass a subset of this information such that the user can be roughly geolocated without exposing their identity. Cloudflare runs an Anycast network, we do geographic load balancing by terminating the user's connection at our closest point of presence (as determined by BGP) and then routing their traffic to the origin of the customer's choice from there. As we're not doing geo load balancing using DNS, I'm not sure what the information provided by 1.1.1.1 would do for us.
paulsutter 8y ago
This is surely anycast-based geo for dns, not dns-based geo (which couldnt work for dns)

r-w 8y ago

Please do your research. “Any data Cloudflare handles as a result of its resolver for Firefox is as a date processor acting pursuant to Firefox’s data processing instructions. Therefore, the data Cloudflare collects and processes pursuant to its agreement with Firefox is not covered by the Cloudflare Privacy Policy. As part of its agreement with Firefox, Cloudflare has agreed to collect only a limited amount of data about the DNS requests that are sent to the Cloudflare Resolver for Firefox via the Firefox browser. Cloudflare will collect only the following information from Firefox users: […] All of the above information will be stored briefly as part of Cloudflare’s temporary logs, and then permanently deleted within 24 hours of Cloudflare’s receipt of such information.” source: https://developers.cloudflare.com/1.1.1.1/commitment-to-privacy/privacy-policy/firefox/ https://developers.cloudflare.com/1.1.1.1/commitment-to-priv...

bluejekyll 8y ago
> ... DNS requests that are sent to the Cloudflare Resolver for Firefox via the Firefox browser. Is this Firefox specific (via HTTP headers or EDNS options) or is this just the general policy of the 1.1.1.1 resolver for all users?
- sp332 8y ago
  The original article says they're not using CloudFlare's normal DNS-over-HTTPS endpoint, so this is probably specific to Firefox. Edit: according to https://www.cloudflare.com/privacypolicy/ https://www.cloudflare.com/privacypolicy/ the normal privacy policy applies to users of CloudFlare's DNS.

zackbloom 8y ago

The reason we (Cloudflare) don't share ECS info is to protect the privacy of the querying user by not exposing their full IP address to the authoritative resolver. We are exploring ways we can pass a subset of this information such that the user can be roughly geolocated without exposing their identity. Cloudflare runs an Anycast network, we do geographic load balancing by terminating the user's connection at our closest point of presence (as determined by BGP) and then routing their traffic to the origin of the customer's choice from there. As we're not doing geo load balancing using DNS, I'm not sure what the information provided by 1.1.1.1 would do for us.

paulsutter 8y ago

This is surely anycast-based geo for dns, not dns-based geo (which couldnt work for dns)