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. Operyl+Od[view] [source] 2019-10-04 08:44:32
>>Thorre+Qc
They’re intentionally not sending an optional extension, that seems .. fair honestly.
◧◩◪◨
4. cnst+Ge[view] [source] 2019-10-04 08:58:50
>>Operyl+Od
The EDNS-Client-Subnet extension was not meant to be optional for folks running a CDN or a huge public resolver across 100+ POPs.
◧◩◪◨⬒
5. lagadu+nf[view] [source] 2019-10-04 09:10:33
>>cnst+Ge
"Was not meant" means nothing. It's specified as optional because it's an extension mechanism.
[go to top]