Live data from Hacker News

What’s Next in Making Encrypted DNS-over-HTTPS the Default

blog.mozilla.org

161–170 of 191 posts

Re: What’s Next in Making Encrypted DNS-over-HTTPS the Default

#161

Earlier quoted context omitted.

They're not threatening to use DNS-over-HTTPS either. But didn't iOS get browser adblocking capability in the last couple years?

Not for third-party browsers like Chrome or Firefox. In a classic Apple-move, it’s for Safari only.

Even though those browsers have to use a safari core anyway? How strange.

Re: What’s Next in Making Encrypted DNS-over-HTTPS the Default

#162
post #139
post #112

Earlier quoted context omitted.

So now we need to worry about making custom DNS config for every single app on a computer?! It’s absurd.

Does your OS allow you to configure global DNS-over-HTTPS settings? Then you can hardly blame apps for not importing them. Yes, getting rid of shitty old standards means we have to live with multiple in parallel for a while and in the mean time bear additional complexity/work. Otherwise civilization will never advance.

My OS (glibc, specifically) provides a way to resolve names (gethostbyname) using various means (hosts file, mDNS, DNS, directory service) configured by nsswitch.conf. Some distributions (e.g. Ubuntu) even move this to a separate daemon (systemd-resolved) which does stuff like DNSSEC validation and DNS-over-TLS (DNS-over-HTTPS is not (yet) supported natively, you need an extra program for this). I don't think moving common functionality from the OS into individual applications is "getting rid of shitty old standards", we will end up with multiple duplicated implementations.

Re: What’s Next in Making Encrypted DNS-over-HTTPS the Default

#163
post #76

Earlier quoted context omitted.

> DNS is used by ISPs to sell user's data Claims like these keep surfacing in every discussion. While it is good to contemplate what your ISP spying on you would look like and what you can do to minimize that risk, it is not good to present this as normal behaviour. From my perspective I am absolutely certain that this is not something that is routinely done, not in established ISPs in democratic countries. The risks…

How are you so certain that this doesn't happen in general?

Is there any evidence suggesting that it does?

Personally I have no idea whether or not this is a common practice, though I have to agree with xorcist that it's certainly not a given.

Re: What’s Next in Making Encrypted DNS-over-HTTPS the Default

#164
post #44

Earlier quoted context omitted.

They already stated in the article that if the canary domain will be abused they will disable that check.

Yeah. Sounds like another do-not-track then. I’ll keep my firewall-rules banning all DoH-traffic to Cloudflare, just in case.

I suppose you can block the IP 1.1.1.1, but Google serves THEIR DNS at `google.com` on HTTPS port. One of the design choices of DoH to make it look like HTTPS traffic.

It's gonna be difficult to block DoH traffic.

Re: What’s Next in Making Encrypted DNS-over-HTTPS the Default

#165
post #45

Earlier quoted context omitted.

I guess thats Mozillas new monetizing strategy, sell user data to cloudflare, and market it as privacy. If you want privacy you better firewall everything your computer want to send to Cloudflare, Akamai, et.al.

Good luck with blocking Cloudflare and Akamai and still using the internet.

It's not that bad. Done it before. It's as if some sites are more like other paywalled sites.maybe noscript trained me well for it.

Re: What’s Next in Making Encrypted DNS-over-HTTPS the Default

#166
Why would Mozilla hurt Firefox's market share in such an obvioud and drastic way? Do they not have anyone at their meetings that brings up obvious and uncomfortable risks?

I use DoH on Firefox and love it but man, I myself would block Firefox in a corporate network I help oversee if this is the default. Matter of fact, web proxies already list DoH resolvers as anonymizing sites.

Even if this involves some profit with cloudflare,this is strategically terrible for long term goals.

Re: What’s Next in Making Encrypted DNS-over-HTTPS the Default

#167

Earlier quoted context omitted.

Not for third-party browsers like Chrome or Firefox. In a classic Apple-move, it’s for Safari only.

Even though those browsers have to use a safari core anyway? How strange.

Technically speaking they are not using Safari, but a WebView.

Re: What’s Next in Making Encrypted DNS-over-HTTPS the Default

#168

Earlier quoted context omitted.

And DNSSEC all the way to the user!

I'd be pretty pissed if my network connection opted me into a DNSSEC-verifying resolver, since that is pretty much pure downside for users.

As someone not very knowledgable about DNSSEC, can you expand on this point? To the uninformed that sounds very counterintuitive.

Re: What’s Next in Making Encrypted DNS-over-HTTPS the Default

#169

So what will be « safer » ? Using a pi-hole or equivalent, or using this ? IIRC all DoH requests are sent to Cloudflare. Is there a way to host your own DNS server and use it with DoH instead ?

Yeah, you can re-configure Pi-Hole to use DoH (with your preferred servers). unbound can be configured to use DoH as well.

For unbound, I just dropped this in my /etc/unbound/unbound.conf.d/02-block-doh.conf

  local-zone: "use-application-dns.net" static

Re: What’s Next in Making Encrypted DNS-over-HTTPS the Default

#170

Earlier quoted context omitted.

I'd be pretty pissed if my network connection opted me into a DNSSEC-verifying resolver, since that is pretty much pure downside for users.

As someone not very knowledgable about DNSSEC, can you expand on this point? To the uninformed that sounds very counterintuitive.

His blog post: https://sockpuppet.org/blog/2015/01/15/against-dnssec/
Post reply on HN