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. doogli+xp[view] [source] 2019-10-04 11:44:43
>>Thorre+Qc
Do you have a source for this?
◧◩◪◨
4. Thorre+G92[view] [source] 2019-10-05 01:55:40
>>doogli+xp
Sources for archive.is blocking Cloudflare's datacenters:

The exact same command fails when sent from Cloudflare's datacenters, but succeeds when sent from DigitalOcean:

https://community.cloudflare.com/t/archive-is-error-1001/182...

Two more sources:

https://news.ycombinator.com/item?id=19830258

https://news.ycombinator.com/item?id=19829036

[go to top]