<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: DNS over HTTPS (DoH) in Privacy</title>
    <link>https://community.isc2.org/t5/Privacy/DNS-over-HTTPS-DoH/m-p/35666#M1041</link>
    <description>&lt;P&gt;Any idea how it deals with split-brain DNS?&amp;nbsp; That is, my company supplies different results to internal vs public queries?&lt;/P&gt;</description>
    <pubDate>Thu, 14 May 2020 14:29:09 GMT</pubDate>
    <dc:creator>denbesten</dc:creator>
    <dc:date>2020-05-14T14:29:09Z</dc:date>
    <item>
      <title>DNS over HTTPS (DoH)</title>
      <link>https://community.isc2.org/t5/Privacy/DNS-over-HTTPS-DoH/m-p/34351#M1010</link>
      <description>&lt;P&gt;Today's privacy tip: Secure your DNS Queries using DoH&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;DNS over HTTPS (DoH) enables Domain Name System (DNS) resolution via the HTTPS protocol.&amp;nbsp;&lt;SPAN&gt;DoH allows users to encrypt DNS traffic by using a TLS channel directly to a single provider they trust - Chrome actually supports 7 different providers.&amp;nbsp;&lt;/SPAN&gt;&lt;SPAN&gt;Configuring Chrome to use DoH is as straightforward&amp;nbsp;as enabling the #dns-over-https flag (type ‘&lt;A href="https://flags/#dns-over-https" target="_blank"&gt;chrome://flags/#dns-over-https&lt;/A&gt;‘ in the ominbox) then select ‘enabled’ from the drop-down menu. You too can live on the experimental&amp;nbsp;edge and keep your searches private. For more on DoH and much more check out this &lt;A href="https://research.nccgroup.com/2020/03/30/impact-of-dns-over-https-doh-on-dns-rebinding-attacks/" target="_blank" rel="noopener"&gt;research paper&lt;/A&gt;.&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 01 Apr 2020 00:48:05 GMT</pubDate>
      <guid>https://community.isc2.org/t5/Privacy/DNS-over-HTTPS-DoH/m-p/34351#M1010</guid>
      <dc:creator>AppDefects</dc:creator>
      <dc:date>2020-04-01T00:48:05Z</dc:date>
    </item>
    <item>
      <title>Re: DNS over HTTPS (DoH)</title>
      <link>https://community.isc2.org/t5/Privacy/DNS-over-HTTPS-DoH/m-p/35645#M1040</link>
      <description>&lt;P&gt;Is it true that DoH is a DNS-specific implementation of HTTPS Over Multiple Enterprise Resources?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Craig&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 14 May 2020 03:17:58 GMT</pubDate>
      <guid>https://community.isc2.org/t5/Privacy/DNS-over-HTTPS-DoH/m-p/35645#M1040</guid>
      <dc:creator>CraginS</dc:creator>
      <dc:date>2020-05-14T03:17:58Z</dc:date>
    </item>
    <item>
      <title>Re: DNS over HTTPS (DoH)</title>
      <link>https://community.isc2.org/t5/Privacy/DNS-over-HTTPS-DoH/m-p/35666#M1041</link>
      <description>&lt;P&gt;Any idea how it deals with split-brain DNS?&amp;nbsp; That is, my company supplies different results to internal vs public queries?&lt;/P&gt;</description>
      <pubDate>Thu, 14 May 2020 14:29:09 GMT</pubDate>
      <guid>https://community.isc2.org/t5/Privacy/DNS-over-HTTPS-DoH/m-p/35666#M1041</guid>
      <dc:creator>denbesten</dc:creator>
      <dc:date>2020-05-14T14:29:09Z</dc:date>
    </item>
  </channel>
</rss>

