<story><title>NextDNS Joins Firefox’s Trusted Recursive Resolver</title><url>https://blog.mozilla.org/blog/2019/12/17/firefox-announces-new-partner-in-delivering-private-and-secure-dns-services-to-users/</url></story><parent_chain></parent_chain><comment><author>3xblah</author><text>“For most users, it’s very hard to know where their DNS requests go and what the resolver is doing with them.” said Eric Rescorla, Firefox CTO. “Firefox’s Trusted Recursive Resolver program &lt;i&gt;allows Mozilla to negotiate with providers on your behalf&lt;/i&gt; and require that they have strong privacy policies before handling your DNS data. We’re excited to have NextDNS partner with us in our work &lt;i&gt;to put people back in control of their data and privacy online&lt;/i&gt;.”&lt;p&gt;It sounds more like the work is to put Mozilla and their partners in control of users&amp;#x27; data and privacy online.&lt;p&gt;Let&amp;#x27;s be honest.  This is really a transfer of control from one third party, e.g., a company providing internet service (ISP), to another third party, e.g., a company&amp;#x2F;organization providing a browser (Mozilla, Google, etc.), not to mention their &amp;quot;TRR&amp;quot; partners.&lt;p&gt;Surely it is only a fortuitous coincidence, but DOH in the browser makes it easier to track users &lt;i&gt;by device&lt;/i&gt;, which appears to be the Holy Grail of the internet ad industry.&lt;p&gt;Putting Mozilla (and their partners) in charge of user privacy is different from putting users in charge of their own privacy.&lt;p&gt;Also, the &amp;quot;back in control&amp;quot; language is interesting.  It implies the author believes users were &amp;quot;in control&amp;quot; in the past.</text></comment>
<story><title>NextDNS Joins Firefox’s Trusted Recursive Resolver</title><url>https://blog.mozilla.org/blog/2019/12/17/firefox-announces-new-partner-in-delivering-private-and-secure-dns-services-to-users/</url></story><parent_chain></parent_chain><comment><author>heavyset_go</author><text>I&amp;#x27;m a fan of DoH, but I&amp;#x27;m also a Chromecast owner, so I get to experience the downsides of application-level DNS resolvers. Chromecasts will ignore the DNS servers set by DHCP, and will cease to function if they cannot communicate with Google&amp;#x27;s DNS servers[1].&lt;p&gt;That means my network-enforced DNS preferences that block ad and malware sources are ignored, and I see more ads than I want to. It also means that when Google drops support for my Chromecast model like they did with the older Chromecast models, I&amp;#x27;ll be slightly less secure than I would be if I could enforce my own DNS preferences.&lt;p&gt;[1] &lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;news.ycombinator.com&amp;#x2F;item?id=19170671&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;news.ycombinator.com&amp;#x2F;item?id=19170671&lt;/a&gt;</text></comment>