Re:DNS-over-HTTPS
by deathanatos on Thursday September 29, 2016 @11:12PM
(#12610333)
So, what DNS server do you use? I trust Google's DNS (I use the normal DNS ones, 8.8.8.8 and 8.8.4.4) a lot more than I trust Comcast's DNS servers. I'm sure there are others out there, of course, but 8.8.8.8 is good, reliable, and easily memorized.
[ Parent
| on HN ]
I run my own, but then again, I also run my own web and email services. But in my gut, I have the feeling that at some point, Google will become the Internet (or even worse---we have the GoogleNet and FacebookNet and never the twain shall share).
Until then, I'll run my own stuff.
> So, what DNS server do you use?
The chaos computer club runs their own, which happens to answer usually just as fast as Google’s DNS. (And which isn’t subject to censorship, Google’s DNS, like Comcast and most US ISPs, censor several domains of piracy websites, although the domains are still existing in the ICANN database, and are reachable through most other DNS servers)
Re:DNS-over-HTTPS
by robertcope on Friday September 30, 2016 @07:34AM
(#12611834)
I use OpenDNS. My home network is setup so that all DNS requests are sent via dnscrypt to OpenDNS. This ensures that Comcast (or whoever) doesn't ever see my DNS traffic and can't muck with it.
Comcast is the one sending you the (unsigned, unencrypted) response packets from 8.8.8.8.
You might as well use the Comcast ones.
Re:DNS-over-HTTPS
by Dylan16807 on Friday September 30, 2016 @11:04AM
(#12612861)
Politically it's a lot easier to stop Comcast from altering through-traffic DNS than it is to stop them from lying in DNS responses and calling it pro-user.
Re:DNS-over-HTTPS
by sashametro on Friday September 30, 2016 @02:33PM
(#12614315)
And if you use DNS-over-HTTPS to get your answers from Google, Comcast can't modify them.