Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

1.1.1.1 Cloudflare DNS Resolver Soon to Be Announced?

webcache.googleusercontent.com

Post reply on HN
Print view View original

91–100 of 253 posts

Re: 1.1.1.1 Cloudflare DNS Resolver Soon to Be Announced?

#91

Post by michaelmior »

duskwuff wrote: post #53
mulmen wrote: post #49

Earlier quoted context omitted.

For "easy to remember" my preference is to use Level 3 because I don't (directly) use them for any other service. 4.2.2.1 4.2.2.2 For as often as I manually configure DNS (I use DHCP) it's not onerous to look up the IPs of whatever DNS is preferable for your purpose. edit: Depending on who you are this may redirect you to a search portal. Probably best to find an alternate DNS provider.

Level 3's resolvers will return fake NXDOMAIN responses that redirect to searchguide.level3.com.

I thought NXDOMAIN responses indicated that the domain doesn't exist and there wasn't a way to actually direct the user anywhere. Your resolver could of course lie and return an IP instead of NXDOMAIN however. Perhaps I'm wrong.

Re: 1.1.1.1 Cloudflare DNS Resolver Soon to Be Announced?

#92

Post by zackbloom »

gsich wrote: post #5
ocdtrekkie wrote: post #2

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.

Do Cloudflare websites work from TOR then?

CF invest a lot of work into Privacy Pass, which is a crypto token system to allow TOR browsers to verify they're human without giving up anonymity: https://privacypass.github.io/

Re: 1.1.1.1 Cloudflare DNS Resolver Soon to Be Announced?

#93

Post by discussedbefore »

gsich wrote: post #59
gpm wrote: post #15

Earlier quoted context omitted.

Up to the website operator. Cloudflare actually went out of their way to make it easy to whitelist Tor IPs that would generally get automatictly blacklisted for abuse.

Not up to the website operator. If Cloudflare blocks TOR or annoys them with Captchas it's Cloudflares problem.

It may be opt-in, but website operators can choose to whitelist Tor even on the free Cloudflare tier.

https://support.cloudflare.com/hc/en-us/articles/203306930-D...

The options for Tor are:

Whitelist (trust)

CAPTCHA (visible challenge which the visitor must interact with to pass)

JavaScript Challenge (visible challenge with less friction, testing the browser)

Block (blacklist -- available only to Cloudflare Enterprise customers)

Re: 1.1.1.1 Cloudflare DNS Resolver Soon to Be Announced?

#94

Post by ebikelaw »

detaro wrote: post #43
ebikelaw wrote: post #41

Earlier quoted context omitted.

The privacy statements on this service are vague. Google makes specific and strong guarantees about what it does with DNS service logs. Google does not keep DNS logs with client IPs longer than 48 hours. I also note that Cloudflare doesn't make a performance comparison with Google DNS.

"We will never log your IP address" doesn't sound that vague.

But it is. They don't say what they do log. For example if I zero out the highest octet of your IP address and I log the ASN, I have effectively identified you without "logging your IP address".

Re: 1.1.1.1 Cloudflare DNS Resolver Soon to Be Announced?

#95

Post by gruez »

cm2187 wrote: post #64
gruez wrote: post #51

Earlier quoted context omitted.

Most ISPs provide their own DNS server via dhcp, why not use that?

For servers you typically have no DHCP. Also ISP often have annoying behaviours like redirecting you to their own websites for failed lookups. And my ISP doesn’t allow local non routable IPs (192.168.1.x) in DNS responses while google does.

>And my ISP doesn’t allow local non routable IPs (192.168.1.x) in DNS responses

isn't that the recommended behavior? otherwise you can do a bunch nasty stuff like rebinding attacks.

https://www.ietf.org/proceedings/52/I-D/draft-ietf-dnsop-don...

Re: 1.1.1.1 Cloudflare DNS Resolver Soon to Be Announced?

#96

Post by xxdesmus »

gsich wrote: post #59
gpm wrote: post #15

Earlier quoted context omitted.

Up to the website operator. Cloudflare actually went out of their way to make it easy to whitelist Tor IPs that would generally get automatictly blacklisted for abuse.

Not up to the website operator. If Cloudflare blocks TOR or annoys them with Captchas it's Cloudflares problem.

nope -- as stated, up to the website owner. They can whitelist Tor if they'd like to. Entirely the website owner's decision to make.

Re: 1.1.1.1 Cloudflare DNS Resolver Soon to Be Announced?

#97

Post by bogomipz »

mrb wrote: post #46

Wonder how much it cost Cloudflare to buy 1.1.1.0/8 from China Telecom...

Where did you get China Telecom from? The IANA released 1.0.0.0/8 to APNIC in 2010 and 1.1.1.0/24 was assigned to APNIC-LABS. The IRR Netname is actually still APNIC-LABS too. See:

https://stat.ripe.net/1.1.1.1#tabId=at-a-glance

Re: 1.1.1.1 Cloudflare DNS Resolver Soon to Be Announced?

#98

Post by xxdesmus »

f2n wrote: post #30
gpm wrote: post #15

Earlier quoted context omitted.

Up to the website operator. Cloudflare actually went out of their way to make it easy to whitelist Tor IPs that would generally get automatictly blacklisted for abuse.

They also went out of their way to automatically treat them as more questionable by default. Unless the website operator explicitly whitelists tor, tor users are given a worse experience. EDIT: Maybe not anymore? See replies

"They also went out of their way to automatically treat them as more questionable by default."

nope, you're spreading un-sourced/unconfirmed FUD. Provide a source, or this is just FUD. Tor IPs are treated like any other IP by default, not "more questionable by default".

Re: 1.1.1.1 Cloudflare DNS Resolver Soon to Be Announced?

#100

Post by f2n »

xxdesmus wrote: post #98
f2n wrote: post #30

Earlier quoted context omitted.

They also went out of their way to automatically treat them as more questionable by default. Unless the website operator explicitly whitelists tor, tor users are given a worse experience. EDIT: Maybe not anymore? See replies

"They also went out of their way to automatically treat them as more questionable by default." nope, you're spreading un-sourced/unconfirmed FUD. Provide a source, or this is just FUD. Tor IPs are treated like any other IP by default, not "more questionable by default".

Perhaps they've changed it since last time I looked a few years ago. You're right, I can't find the tor-specific anything anymore. I ditched Cloudflare years ago and haven't checked back in a while. I rather distinctly remember a default setting that explicitly talked about how it treated Tor users. I don't see that setting anymore.
Post reply on HN