Hacker News Reader

Comment by Buge | Hacker News Reader

The article claims that 1.1.1.1 is a joint project between CloudFlare and Mozilla. But the source it links to for that never mentions Mozilla.

View on HN

Is this article better [1]? Mozilla has partnered with Cloudflare to provide direct DNS resolution from within the Firefox browser using the Cloudflare Resolver for Firefox. What this means is that whenever you click on or type a web address in the Firefox browser your DNS lookup request will be sent over a secure channel to the Cloudflare Resolver for Firefox rather than to an unknown DNS resolver, significantly decreasing the odds of any unwanted spying or man in the middle attacks.

[1] https://developers.cloudflare.com/1.1.1.1/commitment-to-priv...

That just says that Firefox is going to use 1.1.1.1 . But this Freedom to Tinker article is saying Mozilla helps operate 1.1.1.1 and that Mozilla has partial ownership.

>Mozilla and Cloudflare are deploying their own DNS recursive resolver

>Mozilla/Cloudflare’s 1.1.1.1 operate such open DNS recursive resolvers

Great, so all my internal DNS names just fail? Some of those override external names (e.g. dailymail.co.uk at home points to a holding page in case I accidentally click a link to that vile piece of trash)

And on my isolated network, which has no routed access to the internet?

hopefully there is at least an option to disable that.

At this point your best bet is to get it straight from the source https://bugzilla.mozilla.org/show_bug.cgi?id=1434852

> Provides an optional resolver mechanism for Firefox that allows running together with or instead of the native resolver.

> "localhost" and names in the ".local" TLD will never be resolved via DOH.

> TRR is preffed OFF by default

Does it mean Firefox will work without having DNS configured at OS level and just force you to use 1.1.1.1 or what? Cannot find any information on mozilla.org

Only for DNS over HTTPS, which Firefox Nightly can deal with itself: https://www.ghacks.net/2018/04/02/configure-dns-over-https-i...

I know that Mozilla just spent the past weekend doing a bunch of work on both their internal- and external-facing DNS infrastructure, but I don't believe it had anything to do with this.

WRT to the Cloudflare/Mozilla "partnership", see this discussion [0] from 11 days ago (spoiler: it's a "Shield study").

[0]: https://news.ycombinator.com/item?id=16653889

Reply on news.ycombinator.com