[ndiddy]

The operator of archive.is got fed up with dealing with legal notices, so he set up his CDN so that accessing the site from any given country would get served by a server in a neighboring country (meaning that a takedown would involve international cooperation, so it would almost never be worth the effort). DNS requests have an optional field (EDNS client subnet) that provides part of the user's IP address so the CDN can respond with the closest possible server to the user, which is how archive.is does its country mitigation thing. Cloudflare's DNS does not provide this field. They say it's an anti-tracking move, others have speculated it's a competitive move since it means that Cloudflare will know where a user is located but competing CDNs won't. Because not knowing where a user is located before serving them would cause archive.is trouble, they respond to any DNS queries without the EDNS client subnet information with bad data.

[vanchor3]

> he set up his CDN so that accessing the site from any given country would get served by a server in a neighboring country (meaning that a takedown would involve international cooperation, so it would almost never be worth the effort)

I don't really see how this prevents that issue. They still have a server in that country. Just because the DNS name doesn't always point there doesn't seem like it should shield them from legal trouble.