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. Stream+9j[view] [source] 2019-10-04 10:08:30
>>Thorre+Qc
And I agree with that as a Cloudflare customer. In fact if this was a paid feature I would pay for it.

Just to give you more insight. Google knows which IP address I am using Gmail from. If I use 8.8.8.8 they know what other content I am looking for which websites I visit and tie that to my account. If I use something like Cloudflare who do not expose my IP (or range) then I achieved more privacy. I could use my local DNS server (like I do at home) but I travel a lot.

In this case "misconfiguration" is actually for privacy and archive.is could live with that just like other sites but they intentionally screw with Cloudflare (aka the users who has 1.1.1.1 as the resolver).

[go to top]