Hacker News Reader

A couple of issues with the title. The 1st is that archive.* not resolving isn't accurate. archive.today and the other domains associated with it such as archive.is fail to resolve. archive.org which is not associated resolves fine. The same for archive.us (a parked domain). Also the title implies the issue is with Cloudflare when the issue is archive.today refusing to answer dns requests from Cloudflare.

View on HN

Edited Title to reflect archive.(today|is|li|vn|fo|md)

archive.today resolves correctlly from other DNS providers, it is just Cloudflare resolving incorrectly.

Cloudflare strips the edns info from requests. Edns contains the IP address of the client making the request. Cloudflare strips it for privacy reasons. archive.today has an issue with this and therefore refuses to answer dns requests from Cloudflare. According to archive.today this is because not having the requesting IP address prevents them from complying with per country requirements. But archive.today will happily reply to dns requests from other resolvers which don't include the edns info. You can test this yourself using dig with the +noedns flag.

This would seem like a childish dispute, and if you follow my previous postings on this subject,

you would see Cloudflare resolved to 1.1.1.(4|6|7|8) all Cloudflare IPs, not an IP that archive.today would provide

Reply on news.ycombinator.com