News for hackers. Stuff that matters.

A comment on 1.1.1.1 Cloudflare DNS Resolver Soon to Be Announced?. Parent comment

Re:1.1.1.1 Cloudflare DNS Resolver Soon to Be Announced? by gruez on Friday March 30, 2018 @12:12PM (#16717341)
Most ISPs provide their own DNS server via dhcp, why not use that?
[ Parent | on HN ]
Re:1.1.1.1 Cloudflare DNS Resolver Soon to Be Announced? by manacit on Friday March 30, 2018 @12:23PM (#16717443)
My ISP (Spectrum / Time Warner) will not return a proper NXDOMAIN, and will instead send you to an ad-filled "search" page. They're also slower than Google DNS somehow, and generally not much more than an opportunity for my ISP to get more information and ad revenue from me.

At least I'm not paying Google to do the same, and I can trust that they'll send the proper results.

[ Parent | on HN ]
Re:1.1.1.1 Cloudflare DNS Resolver Soon to Be Announced? by gsich on Friday March 30, 2018 @12:19PM (#16717404)
Because most of them suck (Censorship, NXDOMAIN fuckups). Or are not reachable outside the ISP network.
[ Parent | on HN ]
Re:1.1.1.1 Cloudflare DNS Resolver Soon to Be Announced? by cm2187 on Friday March 30, 2018 @12:19PM (#16717401)
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.
[ Parent | on HN ]
Re:1.1.1.1 Cloudflare DNS Resolver Soon to Be Announced? by gruez on Friday March 30, 2018 @12:44PM (#16717651)
>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...

[ Parent | on HN ]
Re:1.1.1.1 Cloudflare DNS Resolver Soon to Be Announced? by thisacctforreal on Friday March 30, 2018 @10:20PM (#16721294)
It's necessary for adding SSL to an intranet service.
[ Parent | on HN ]