4 ms·

For performance and privacy reasons, you should use Cloudflare DNS. Please don't trust blindly Google when they say they don't use your DNS request data. It is

For performance and privacy reasons, you should use Cloudflare DNS. Please don't trust blindly Google when they say they don't use your DNS request data. It is their core business model to get their hand on all the data they can. https://blog.cloudflare.com/announcing-1111/ https://blog.cloudflare.com/announcing-1111/

rascul 8y ago
It's not clear to me that I can trust Cloudflare, either.
- ironjunkie 8y ago
  I will take the least of two evils. Look at the incentive and core business of the two companies. Cloudflare is not in the business of mining as much data about you as possible. They don't sell ads and don't make money trying to make you fit into a profile. They have zero incentive to keep an history of all your DNS requests. Google on the other hand, claim they don't do it but it will make complete sense for their business to do it.
  - anothergoogler 8y ago
    Given their security track record, I wouldn't trust Cloudflare with any of my data, regardless of what they plan or don't plan on doing with it.
    - noncoml 8y ago
      > Given their security track record, I wouldn't trust Cloudflare with any of my data, regardless of what they plan or don't plan on doing with it. Your username is anothergoogler; do you work for Google?
      - anothergoogler 8y ago
        No, but I do search using Google.
        noncoml 8y ago
        Oh, ok. Sorry. Usually it Google employees that call themselves "Googlers"
fickyrigil 8y ago
So blindly trust Cloudflare instead of Google?
- deleted 8y ago
  [deleted]
grier 8y ago
So it's fine to trust cloudflare "blindly" with the same data? (I agree that for privacy DNS over https is good, but the resolver still sees your dns queries)
- chewz 8y ago
  Don't trust any corporation. It is unbelivable simple to install dnscrypt-proxy 2 [1] and use DNS crypt. Dnscrypt-proxy spreads your queries across multiple servers and keeps them private. If you can afford consider running dnscrypt server yourself. [2] [1] https://github.com/jedisct1/dnscrypt-proxy https://github.com/jedisct1/dnscrypt-proxy [2] https://github.com/jedisct1/dnscrypt-proxy/wiki/How-to-setup-your-own-DNSCrypt-server-in-less-than-10-minutes https://github.com/jedisct1/dnscrypt-proxy/wiki/How-to-setup...
tills13 8y ago
This is nothing more than pure conjecture...
zavi 8y ago
Asserted without evidence, dismissed without evidence.
0xb100db1ade 8y ago
Cloudflare's 1.1.1.1 DNS blocks https://archive.is https://archive.is
- jasonkostempski 8y ago
  Why?
- caymanjim 8y ago
  I didn't believe they'd do something like this, so I went to check and prove you wrong, but sure enough, it doesn't resolve. According to this post on CloudFare's support site, it's not their fault: https://community.cloudflare.com/t/archive-is-error-1001/18227 https://community.cloudflare.com/t/archive-is-error-1001/182.... > This is unfortunately something we can’t do something about. Nameservers responsible for archive.is (ben.archive.is, anna.archive.is) are returning answers tailored to the IP address of the requestor.
  - shakna 8y ago
    And archive.is blames CloudFlare: > it is because of 1.1.1.1 > try 8.8.8.8 But compare that answer, to the continued technical breakdowns given by CloudFlare as they tried to work out why archive.is is returning an inaccessible IP based an request IP. CloudFlare attempted to determine why there was a problem, archive.is shrugged it off.
  - nmjohn 8y ago
    I did the same research because I too found it hard to believe and it's still not clear to me how the problem is not on cloudflare. They claim the upstream is misconfigured, but how then does every single other DNS provider manage to handle it correctly? Or are they claiming archive.is is explicitly blacklisting the cloudflare IP range? If that is the case it seems odd they are claiming the upstream is misconfigured as opposed to explicitly blocking them. Something does not add up correctly.
    - meta_AU 8y ago
      Sometimes 1.1.1.1 is used as a testing value, and can get blocked for reasons. CloudFlare is getting a huge amount of spam IP traffic to 1.1.1.1 from misconfigured equipment, it wouldn't be too surprising if some upstreams have firewalled valid IPs.
gonyea 8y ago
Baseless fear mongering from a concern troll.
LambdaComplex 8y ago
Cloudflare manipulated DNS entries in the recent past[0], so I don't think I want to use them. 0. https://twitter.com/eastdakota/status/1024018061311897600 https://twitter.com/eastdakota/status/1024018061311897600

rascul 8y ago

It's not clear to me that I can trust Cloudflare, either.

ironjunkie 8y ago
I will take the least of two evils. Look at the incentive and core business of the two companies. Cloudflare is not in the business of mining as much data about you as possible. They don't sell ads and don't make money trying to make you fit into a profile. They have zero incentive to keep an history of all your DNS requests. Google on the other hand, claim they don't do it but it will make complete sense for their business to do it.
- anothergoogler 8y ago
  Given their security track record, I wouldn't trust Cloudflare with any of my data, regardless of what they plan or don't plan on doing with it.
  - noncoml 8y ago
    > Given their security track record, I wouldn't trust Cloudflare with any of my data, regardless of what they plan or don't plan on doing with it. Your username is anothergoogler; do you work for Google?
    - anothergoogler 8y ago
      No, but I do search using Google.
      - noncoml 8y ago
        Oh, ok. Sorry. Usually it Google employees that call themselves "Googlers"

fickyrigil 8y ago

So blindly trust Cloudflare instead of Google?

deleted 8y ago
[deleted]

grier 8y ago

So it's fine to trust cloudflare "blindly" with the same data? (I agree that for privacy DNS over https is good, but the resolver still sees your dns queries)

chewz 8y ago
Don't trust any corporation. It is unbelivable simple to install dnscrypt-proxy 2 [1] and use DNS crypt. Dnscrypt-proxy spreads your queries across multiple servers and keeps them private. If you can afford consider running dnscrypt server yourself. [2] [1] https://github.com/jedisct1/dnscrypt-proxy https://github.com/jedisct1/dnscrypt-proxy [2] https://github.com/jedisct1/dnscrypt-proxy/wiki/How-to-setup-your-own-DNSCrypt-server-in-less-than-10-minutes https://github.com/jedisct1/dnscrypt-proxy/wiki/How-to-setup...

tills13 8y ago

This is nothing more than pure conjecture...

zavi 8y ago

Asserted without evidence, dismissed without evidence.

0xb100db1ade 8y ago

Cloudflare's 1.1.1.1 DNS blocks https://archive.is https://archive.is

jasonkostempski 8y ago
Why?
caymanjim 8y ago
I didn't believe they'd do something like this, so I went to check and prove you wrong, but sure enough, it doesn't resolve. According to this post on CloudFare's support site, it's not their fault: https://community.cloudflare.com/t/archive-is-error-1001/18227 https://community.cloudflare.com/t/archive-is-error-1001/182.... > This is unfortunately something we can’t do something about. Nameservers responsible for archive.is (ben.archive.is, anna.archive.is) are returning answers tailored to the IP address of the requestor.
- shakna 8y ago
  And archive.is blames CloudFlare: > it is because of 1.1.1.1 > try 8.8.8.8 But compare that answer, to the continued technical breakdowns given by CloudFlare as they tried to work out why archive.is is returning an inaccessible IP based an request IP. CloudFlare attempted to determine why there was a problem, archive.is shrugged it off.
- nmjohn 8y ago
  I did the same research because I too found it hard to believe and it's still not clear to me how the problem is not on cloudflare. They claim the upstream is misconfigured, but how then does every single other DNS provider manage to handle it correctly? Or are they claiming archive.is is explicitly blacklisting the cloudflare IP range? If that is the case it seems odd they are claiming the upstream is misconfigured as opposed to explicitly blocking them. Something does not add up correctly.
  - meta_AU 8y ago
    Sometimes 1.1.1.1 is used as a testing value, and can get blocked for reasons. CloudFlare is getting a huge amount of spam IP traffic to 1.1.1.1 from misconfigured equipment, it wouldn't be too surprising if some upstreams have firewalled valid IPs.

gonyea 8y ago

Baseless fear mongering from a concern troll.

LambdaComplex 8y ago

Cloudflare manipulated DNS entries in the recent past[0], so I don't think I want to use them. 0. https://twitter.com/eastdakota/status/1024018061311897600 https://twitter.com/eastdakota/status/1024018061311897600