I think they are not sending any EDNS IP. Because all Cloudflare’s IPs are geolocated to the US, but they have probably given a list of IP <-> PoP relations to Akamai, Google and the likes. That is not something that is public, but I would assume neither Google nor Akamai would launch a DDoS towards Cloudflare so they feel safe doing that.
From the 18.104.22.168 resolver (22.214.171.124 locally) I can see that an OPT record with EDNS Client Subnet is sent.
From 126.96.36.199 (188.8.131.52 locally) an OPT record is sent but without any extensions.
I guess this is really a feature request, then.
This also seems to affect CNAME flattening in authoritative DNS product as well, which is a bummer. Changing to another DNS host might be on the horizon for me, can’t afford the $200/mo/domain it would take to use be able to use Cloudflare’s CDN in Australia .
The difference is ~ 200ms of latency, which really shows in desktop applications (like outlook).
Its worth nothing this appears to be random. At times I do get AUS results, while other times i get USA/Canada. I get that ECS isn’t exposed for privacy reasons, but perhaps a “bypass” capability in Cloudflared (which is what im using for DNS over HTTPS) may be ideal until geo-location data can be updated accordingly?
Almost a year has passed and the problems are still there … more than 6 months ago they indicated that it was under consideration to enable EDNS … We continue in the sweet wait using GOOGLE DNS, with which if things work correctly …
Are you going to take a lot more time to consider it ???
I said “ALMOST” a year … and it was not a month … If you verify the link that I put, you will see that these problems come from the beginning of the year, when cscharff had already commented that they were “considering” …
With respect to Google, they had mentioned that it was solved … however, most of the time certain connections, in my case, are directed to Peru … rarely within Argentina (EZE).
So I do not see that it is very solved that we say …
I don’t think this will ever be in the roadmap. Of course I am not on the team, but the premise of 184.108.40.206 is privacy and EDNS Client Subnet is the opposite of that. If that’s what you need fine, otherwise there are fine alternatives depending on your location.