zlacker

[return to "Why does 1.1.1.1 not resolve archive.is?"]
1. tedk-4+K9[view] [source] 2019-10-04 07:50:51
>>stargr+(OP)
I really don't see this as a problem of Cloudflare.

End users switching to Cloudflare's DNS endpoint are doing so because they feel the DNS provider is both faster and more secure.

They rightly made the decision NOT to pass on the end user's IP information to the upstream DNS server. I agree with this decision and they are acting in my best interests in doing so. To draw some kind of nefarious intention from this is absurd.

Until Cloudflare are proven to be nefarious actors, I'll continue to use their service.

◧◩
2. varela+fe[view] [source] 2019-10-04 08:52:42
>>tedk-4+K9
That looks like uncompetitive behavior from Cloudflare, so it's their problem also. Cloudflare can send EDNS if nameserver and the actual server run by the same party, but they don't
◧◩◪
3. zzzcpa+ui[view] [source] 2019-10-04 09:57:42
>>varela+fe
Well, yeah. This was one of the significant reasons against Cloudflare's DoH too. They want all Firefox users to use their DNS resolver and deprive the ability of competing DNS-based CDNs (most CDNs) to pick good nodes in Firefox. I've been thinking of blacklisting Cloudflare completely on all of my servers just for that. And it seems Firefox will even be able to detect that and fallback to proper DNS for such domains.
[go to top]