Live data from Hacker News

1.1.1.1 Cloudflare DNS Resolver Soon to Be Announced?

webcache.googleusercontent.com

191–200 of 253 posts

Re: 1.1.1.1 Cloudflare DNS Resolver Soon to Be Announced?

#191
post #14

Well crap. I was used to going to 1.1.1.1 on my cellphone when on wireless APs that tried to redirect you an agreement page. Now there is a valid cert/website at that address. Guess I'll have to pick a new one.

Lots of suggestions here but you can also use http://captive.apple.com

Re: 1.1.1.1 Cloudflare DNS Resolver Soon to Be Announced?

#193
post #39

This is awesome to hear, and for all of the criticism Cloudflare has gotten in the past, they have spoken loudly against censorship, not just for people they like, but those they dislike as well. I'd much rather point my DNS at them than Google, an ad company where tracking is the whole business model.

How much tracking can you do on a v4 DNS? There can be thousands of people behind the same IPv4 at a given time, or it could change in a matter of minutes. A state could probably be able to exploit that (as in there is a political opponent living at this address) but if the aim is just to track an individual’s browsing habit I would think it is impractical. IPv6, other debate.

I have an IPv6 address that has never changed. My IPv4 address changes fairly often. The DHCP servers most definitely log the end-point MAC which can be tied directly by the ISP to my modem and router behind it. It's fairly easy to trace this stuff, if somewhat impractical.

Re: 1.1.1.1 Cloudflare DNS Resolver Soon to Be Announced?

#194

Earlier quoted context omitted.

What about akamai? They are a much larger CDN (no one talks about it on HN because they are not a startup). I agree with your assertion that it will become a single point of failure with many web properties but also I think that HN has a sort of filter bubble on startups (for obvious reasons) and I'm not sure cloudflare is as big as people make it out to be. Also, Google has 8.8.8.8 which could be for the same thing…

CloudFlare publishes their pricing. Akamai doesn't. Dealing with salespeople is a massive PITA. They're not going to tell me anything that's not in the docs or support forums and I don't want to spend a week negotiating. I've seen many others make this point on HN over the years. Maybe Akamai only focuses on large enterprise customers while CloudFlare also goes for the SMB market. IDK. The HN crowd seems to work at S…

Fuck I hate this. I've avoided buying storage servers from ixsystems, despite the fact their products seem to be exactly what we need, because they won't tell me how much they fucking cost. They want to have a "conversation" about "solutions".

Fuck you. Sell me boxes and tell me how much they cost. But they won't.

Re: 1.1.1.1 Cloudflare DNS Resolver Soon to Be Announced?

#195
post #57
post #54

Earlier quoted context omitted.

There's also Quad9 that I saw in an article earlier (not sure if it was on HN).

My personal experience is that I had reliability problems that I didn’t have with Google. And DNS is a critical step in the connection for which you really want reliability.

And mine is the opposite. I have not seen reliability problems with Quad9.

Use cases are different - Quad9 for "nasty" filtered and 8.8.8.8 for err probably not filtered.

Do it yourself otherwise.

Re: 1.1.1.1 Cloudflare DNS Resolver Soon to Be Announced?

#196
post #12

The concerning thing about this is that internet is increasingly dependent on Cloudflare, making it a single point of failure and exploitation. Somehow, people are not talking much about it, but a significant amount of sites have opted in for Cloudflare proxying, allowing it to see the traffic in plain text, while the visitors are made to believe that the connection is secure. Similarly, users will now use their fast…

What about akamai? They are a much larger CDN (no one talks about it on HN because they are not a startup). I agree with your assertion that it will become a single point of failure with many web properties but also I think that HN has a sort of filter bubble on startups (for obvious reasons) and I'm not sure cloudflare is as big as people make it out to be. Also, Google has 8.8.8.8 which could be for the same thing…

So, now we have..... 3 ..... single points of failure ?

I’m clearly missing something, but why doesn’t that solve the problem?

And I’m keeping the scope of my comment on the technical side, and ignoring the business/antitrust potential.

Re: 1.1.1.1 Cloudflare DNS Resolver Soon to Be Announced?

#198
post #177

Earlier quoted context omitted.

CloudFlare publishes their pricing. Akamai doesn't. Dealing with salespeople is a massive PITA. They're not going to tell me anything that's not in the docs or support forums and I don't want to spend a week negotiating. I've seen many others make this point on HN over the years. Maybe Akamai only focuses on large enterprise customers while CloudFlare also goes for the SMB market. IDK. The HN crowd seems to work at S…

Why do startups that sell to other startups hire sales people to do this instead of just having clear pricing? Obviously they must extract some value for the business but the experience of haggling with some sales bro to get a decent price leaves me so annoyed with services that I usually skip signing up when it’s the only option. > Let’s talk about solutions! No thanks. I just want to insert dollars and get the serv…

It's because just having a pricing page doesn't give any feedback as to whether the price is correct or not.

A salesperson could at least ask 'what is a better price we can shoot for?' or 'what features do you really need?' whereas a visitor to a pricing page just disappears.

Re: 1.1.1.1 Cloudflare DNS Resolver Soon to Be Announced?

#199
post #196

Earlier quoted context omitted.

What about akamai? They are a much larger CDN (no one talks about it on HN because they are not a startup). I agree with your assertion that it will become a single point of failure with many web properties but also I think that HN has a sort of filter bubble on startups (for obvious reasons) and I'm not sure cloudflare is as big as people make it out to be. Also, Google has 8.8.8.8 which could be for the same thing…

So, now we have..... 3 ..... single points of failure ? I’m clearly missing something, but why doesn’t that solve the problem? And I’m keeping the scope of my comment on the technical side, and ignoring the business/antitrust potential.

As opposed to further up the stack where you rely on just a small handful of backbones that fail in spectacular ways far more than Cloudflare does. L3 and AT&T and all the networks that just route traffic through China for no reason at all.

As opposed to hosting everything on AWS, so half the Internet goes down when they have a no-so-uncommon outage.

I don’t think Cloudflare is that much of a bottleneck in comparison. Not to mention 3 points of failure is the definition of “not a single point of failure”.

Re: 1.1.1.1 Cloudflare DNS Resolver Soon to Be Announced?

#200
post #12

The concerning thing about this is that internet is increasingly dependent on Cloudflare, making it a single point of failure and exploitation. Somehow, people are not talking much about it, but a significant amount of sites have opted in for Cloudflare proxying, allowing it to see the traffic in plain text, while the visitors are made to believe that the connection is secure. Similarly, users will now use their fast…

What about akamai? They are a much larger CDN (no one talks about it on HN because they are not a startup). I agree with your assertion that it will become a single point of failure with many web properties but also I think that HN has a sort of filter bubble on startups (for obvious reasons) and I'm not sure cloudflare is as big as people make it out to be. Also, Google has 8.8.8.8 which could be for the same thing…

Akamai has 7,500 employees, Cloudflare has 500.
Post reply on HN