<story><title>RFC 7858: DNS over TLS (2016)</title><url>https://tools.ietf.org/html/rfc7858</url></story><parent_chain></parent_chain><comment><author>niftich</author><text>This RFC is from 2016, and isn&amp;#x27;t breaking news, so per HN practice, title should probably have (2016).&lt;p&gt;However, there&amp;#x27;s a March 2018 RFC 8310: &lt;i&gt;Usage Profiles for DNS over TLS and DNS over DTLS&lt;/i&gt; [1] that describes some privacy implications, deployment scenarios, and DNS authentication mechanisms to be used with the new transports.&lt;p&gt;[1] &lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;tools.ietf.org&amp;#x2F;html&amp;#x2F;rfc8310&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;tools.ietf.org&amp;#x2F;html&amp;#x2F;rfc8310&lt;/a&gt;</text></comment>
<story><title>RFC 7858: DNS over TLS (2016)</title><url>https://tools.ietf.org/html/rfc7858</url></story><parent_chain></parent_chain><comment><author>cmurf</author><text>OK so which is more likely to play nice with constantly changing wireless connections? DNS-over-TLS, DNS-over-HTTPS, or DNSSEC? I notice that out of the box, Windows and macOS and Fedora all just defer to the DNS servers that are assigned by DHCP, which come from the local AP. So I&amp;#x27;m pretty much stuck, out of the box, with AP specific DNS policy.</text></comment>