zlacker

[return to "Why does 1.1.1.1 not resolve archive.is?"]
◧
1. profmo+p5[view] [source] 2019-10-04 06:44:52
>>stargr+(OP)
> I consider EDNS-less requests from Cloudflare as invalid.

If your site depends on a DNS extension that's only 3.5 years old (and designed to be optional), I think it's fair to say your site is just offline for some users due to a config mistake.

You're free to set up your servers however you like, but there's wisdom in Postel's law.

◧◩
2. Thorre+Qc[view] [source] 2019-10-04 08:31:14
>>profmo+p5
Archive.is does not block all requests lacking EDNS. They specifically block requests coming from Cloudflare's datacenters. Cloudflare is not accidentally misconfiguring their EDNS, Cloudflare is intentionally not sending EDNS.
◧◩◪
3. lagadu+jf[view] [source] 2019-10-04 09:09:43
>>Thorre+Qc
The "misconfiguration" he's talking about is on archive.is' part. Their configuration expects some specific server to have an optional functionality enabled, which it doesn't.
◧◩◪◨
4. Thorre+Jf[view] [source] 2019-10-04 09:14:52
>>lagadu+jf
Sorry, I don't understand. I was referring to this quote:

> I think it's fair to say your site is just offline for some users due to a config mistake.

Archive.is is not making an accidental mistake. Archive.is is behaving very intentionally. They've said so on Twitter. And I believe profmonocle agrees with me on that point.

◧◩◪◨⬒
5. jgraha+9F[view] [source] 2019-10-04 13:48:08
>>Thorre+Jf
And Cloudflare would happily talk to archive.is to come up with a solution.
[go to top]