zlacker

[return to "Why does 1.1.1.1 not resolve archive.is?"]
◧
1. LeoNat+M3[view] [source] 2019-10-04 06:23:33
>>stargr+(OP)
This is the reason I stopped using 1.1.1.1.
◧◩
2. nobody+84[view] [source] 2019-10-04 06:30:15
>>LeoNat+M3
A very silly one at that given their reasons for not resolving archive.is are quite rational and on the contrary makes me want to swap google's DNS servers for theirs.
◧◩◪
3. tambre+la[view] [source] 2019-10-04 07:58:04
>>nobody+84
> their reasons for not resolving archive.is

They do solve archive.is. But archive.is's DNS servers have been configured to return bogus answers to queries from Cloudflare's servers.

◧◩◪◨
4. nobody+vq[view] [source] 2019-10-04 11:59:55
>>tambre+la
Not cloudflare servers in particular. They demand EDNS(optional by design) which cloudflare does not support due to privacy risks.
◧◩◪◨⬒
5. jlokie+tt[view] [source] 2019-10-04 12:23:52
>>nobody+vq
From https://news.ycombinator.com/item?id=21155852

> Archive.is does not block all requests lacking EDNS. They specifically block requests coming from Cloudflare's datacenters.

◧◩◪◨⬒⬓
6. nobody+9A[view] [source] 2019-10-04 13:15:50
>>jlokie+tt
Wow, what a bunch of not-so-smart people.
[go to top]