Re:DNS Performance compared: CloudFlare 1.1.1.1 x Google 8.8...
by Godel_unicode on Monday April 02, 2018 @11:49PM
(#16741753)
Most people are not very interested in testing how fast their local machine can talk to itself; regardless of how fast your local cache is, it will have to talk outside pretty often (for expiring TTL if nothing else).
[ Parent
| on HN ]
Re:DNS Performance compared: CloudFlare 1.1.1.1 x Google 8.8...
by spc476 on Tuesday April 03, 2018 @12:04AM
(#16741835)
People are praising CloudFlare for not bothering to log requests. Yes, well ... you get the same results by using your own DNS resolver, and you don't have to be shocked when five years later a different governing team running CloudFlare decide to reverse their stance and log everything ...
But what do I know? Apparently I'm in the minority for running my own infrastructure (DNS, web, mail).
Re:DNS Performance compared: CloudFlare 1.1.1.1 x Google 8.8...
by Godel_unicode on Saturday April 07, 2018 @12:20AM
(#16779343)
Where do you think your DNS resolver gets the answers it gives you? You're just introducing a caching layer between you and whatever external resolver you're using. The first time a machine requests a domain (and every time a TTL expires; look at CDN TTLs sometime) you are effectively talking to the internet just like everyone else.
Re:DNS Performance compared: CloudFlare 1.1.1.1 x Google 8.8...
by ragequitta on Tuesday April 03, 2018 @07:27AM
(#16743603)
Do you ever wonder if such activity (basically trying to be invisible) will put you under far more scrutiny than if you were to just 'be normal'? Thinking from the other side of it you would be a high value target to monitor as closely as possible if I were law enforcement. I know it sounds ridiculous but you may actually have more privacy (unless you're actually breaking the law) by hiding in plain sight with the rest of us.
Re:DNS Performance compared: CloudFlare 1.1.1.1 x Google 8.8...
by enneff on Tuesday April 03, 2018 @07:20AM
(#16743570)
If you talk to an upstream resolver through an encrypted link (both CloudFlare and Google support DNSoverTLS and DNSoverHTTPS, at least) then you at least limit the potential privacy threats.