> I wrote the following reply to Matthew, praising his team's focus on the big picture
Okay great, but:
> 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.
> massive mismatch (not only on AS/Country, but even on the continent level) of where DNS and related HTTP requests come
The problem isn't really EDNS. And someone is either lying or very incorrect.
This should be resolvable. The two sides don't want incompatible things. Has there been zero progress since?
>> 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.
Cloudflare makes an exception to this rule for Archive.{today,is,...} domains.
All requests for this domains come from Amazon EC2 in the U.S., not the 180 edges of Cloudflare.
This was on blog.archive.today.
Why? Who knows. But the decision to break up is made by both parties, not just the archive.
Okay great, but:
> 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.
> massive mismatch (not only on AS/Country, but even on the continent level) of where DNS and related HTTP requests come
The problem isn't really EDNS. And someone is either lying or very incorrect.
This should be resolvable. The two sides don't want incompatible things. Has there been zero progress since?