Hacker News Reader

Comment by zamadatix | Hacker News Reader

Actually everyone should prefer the other guy do it rather than host it themselves. Either way the bits have to be transported to the same colocated facilities it's a matter of who has to pay for and operate the servers.

At least Cloudflare has KPMG audit them on their privacy claims. Better than nothing.

View on HN

That made me curious to see who runs KPMG and whether it itself is trustworthy.

There is this: https://en.wikipedia.org/wiki/KPMG#Controversies

and then there is this:

https://home.kpmg/content/dam/kpmg/us/pdf/2019/01/2018-trans...

At the end of the day, any grouping of individuals are a (partially biased) sample of the society in general. The role of media and education is fairly decisive in forming social norms. We may have one or two lost generations of engineers following orders, but as Joe said 'The future is unwritten".

> Actually everyone should prefer the other guy do it rather than host it themselves.

This isn't true. If you're hosting it, you can control it and you can make sure that it's always operational. The last thing you want is a 100 phone call of "my internet isn't working" and then trying to explain it's not your fault, but rather it's "some other guy".

If Google/Cloudflare are having significant issues resolving DNS everybody is getting a call anyways.

Not sure I understand. If you're using your ISP's DNS service, majority of your requests are going to hit their cache. You shouldn't notice any downtime as long as the cache doesn't expire.

I mean if all of Google/Cloudflares anycast resolvers go tits up I'm going to get endless calls regardless if the end user can resolve a cached name or not.

> If you're using your ISP's DNS service

Or you can directly ask a domain's authoritative nameserver directly. Using an intermediate caching resolver isn't required. Recursively resolving the DNS query locally only requires asking a centralized nameserver for a domain's authoritative nameservers (the NS records) which can usually be cashed locally for a long time. Every other request is compartmentalized to different servers by domain delegation.

Or do both; configure your local resolver to try recursively resolving a request, and fall back to the ISP (other) cache if needed.

Tried searching, but couldn’t find a report by KPMG. Has one been produced already or is this a future thing?

Regardless, impressive step to take.

That's a good question, they said it would happen annually so they should have had one by April 1st 2019. I put a question into support, we'll see if it goes anywhere.

Have you checked April 2 for any posts revealing the joke? :)

From the launch page: https://blog.cloudflare.com/announcing-1111/

“Seriously, April 1?

The only question that remained was when to launch the new service? This is the first consumer product Cloudflare has ever launched, so we wanted to reach a wider audience. At the same time, we're geeks at heart. 1.1.1.1 has 4 1s. So it seemed clear that 4/1 (April 1st) was the date we needed to launch it.”

Seems like they were pretty serious with it. :)

Same post mentions KPMG.

Reply on news.ycombinator.com