zlacker

[parent] [thread] 4 comments
1. ikeboy+(OP)[view] [source] 2019-05-04 19:33:12
Besides, my reading is:

Every other resolver supports EDNS

Archive.is only works with resolvers that support EDNS

Cloudflare decided not to support EDNS

That itself is a defendable decision but I do feel for a popular site they could implement some sort of fix.

replies(4): >>tambre+p1 >>akerl_+m2 >>Thorre+e5 >>wolco+Ih
◧
2. tambre+p1[view] [source] 2019-05-04 19:43:19
>>ikeboy+(OP)
Cloudflare does support EDNS. They just don't forward the client's subnet due to being privacy-oriented, doing which is optional and perfectly valid.
◧
3. akerl_+m2[view] [source] 2019-05-04 19:51:43
>>ikeboy+(OP)
Notably, Level3 and Hurricane Electric both appear to not use ECS, and archive.is resolves properly from those. Which seems to clarify that this isn’t a technical requirement for archive.is to work, it’s an intentional protest by the archive.is operators against Cloudflare.
◧
4. Thorre+e5[view] [source] 2019-05-04 20:13:56
>>ikeboy+(OP) 

    dig @carl.archive.is archive.is A +noedns
responds 134.119.220.26

    curl http://134.119.220.26 -H 'Host: archive.is' -v
responds with HTML of the site.

I'm not a dig expert, but I believe this means it works without EDNS. I think that means archive.is is specifically blocking Cloudflare's servers, not blocking all non-EDNS requests.

◧
5. wolco+Ih[view] [source] 2019-05-04 22:33:08
>>ikeboy+(OP)
They need something that works for all sites.
[go to top]