zlacker

>>jahnu+(OP)
It's important to remember, at least for corporate environments, that EDNS Client Subnet is important when working with services such as Exchange Online where the local resolver is what determines your EXO Front Door. If you're using a service like 1.1.1.1, you may be routed to an incorrect Front Door causing increased latency (primarily with search and archive mailboxes which aren't cached).

Quad9 does have a service which provides EDNS Client Subnet support, should you want to leverage it.

>>_akoy+q4
Cloudflare has worked providers to make sure they can efficiently route. If you find case where this isn’t the case please let us know.

>>dknech+Y6
Cloudflare DNS does not route efficiently with AWS CloudFront anycast DNS. I tracked down insanely slow `rustup update` downloads to incorrect selection of ideal routes to the AWS resources caused by using CF to resolve the DNS. Switching to a different resolver that works with anycast and EDNS fixed it.

CF saying “we break standard DNS geo routing but work with providers to route things right” isn’t very inspiring.