<?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: Blocking DNS-over-https in General Topics</title>
    <link>https://live.paloaltonetworks.com/t5/general-topics/blocking-dns-over-https/m-p/319389#M81911</link>
    <description>&lt;P&gt;&lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/71649"&gt;@ce1028&lt;/a&gt;&amp;nbsp; I thought pinning was by choice&lt;/P&gt;</description>
    <pubDate>Mon, 30 Mar 2020 14:11:02 GMT</pubDate>
    <dc:creator>reaper</dc:creator>
    <dc:date>2020-03-30T14:11:02Z</dc:date>
    <item>
      <title>Blocking DNS-over-https</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/blocking-dns-over-https/m-p/319261#M81889</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I plan to create security policy rules to block dns-over-https and dns-over-tls.&amp;nbsp; &amp;nbsp;Is it also recommended to block dnscrypt?&amp;nbsp;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;In regards to dns-over-https.&amp;nbsp; If the browser attempts this and fails, does it fallback to using the client's configured dns servers?&lt;/P&gt;</description>
      <pubDate>Sun, 29 Mar 2020 17:31:12 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/blocking-dns-over-https/m-p/319261#M81889</guid>
      <dc:creator>ce1028</dc:creator>
      <dc:date>2020-03-29T17:31:12Z</dc:date>
    </item>
    <item>
      <title>Re: Blocking DNS-over-https</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/blocking-dns-over-https/m-p/319297#M81894</link>
      <description>&lt;P&gt;the browser should fall back to regular dns if one of the encrypted versions is unavailable.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;why are you blocking these?&lt;/P&gt;</description>
      <pubDate>Mon, 30 Mar 2020 06:36:04 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/blocking-dns-over-https/m-p/319297#M81894</guid>
      <dc:creator>reaper</dc:creator>
      <dc:date>2020-03-30T06:36:04Z</dc:date>
    </item>
    <item>
      <title>Re: Blocking DNS-over-https</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/blocking-dns-over-https/m-p/319373#M81907</link>
      <description>&lt;P&gt;&lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/7608"&gt;@reaper&lt;/a&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Reason for blocking is corporate policy is to allow dns requests from internal DNS servers only.&amp;nbsp; Also, they both create security risks that could allow tunneling of malicious traffic and also could potentially bypass your security policies&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Palo Alto also recommends blocking.&amp;nbsp;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;You don't believe they should be blocked?&amp;nbsp; I'd like to hear your reasons&lt;/P&gt;</description>
      <pubDate>Mon, 30 Mar 2020 13:04:29 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/blocking-dns-over-https/m-p/319373#M81907</guid>
      <dc:creator>ce1028</dc:creator>
      <dc:date>2020-03-30T13:04:29Z</dc:date>
    </item>
    <item>
      <title>Re: Blocking DNS-over-https</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/blocking-dns-over-https/m-p/319377#M81908</link>
      <description>&lt;P&gt;&lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/71649"&gt;@ce1028&lt;/a&gt;&amp;nbsp; i do believe in blocking them, but under the right circumstances &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;my first preference is to block all outbound DNS except the outbound connections from my inhouse DNS server for which i would force tls/https as much as possible (for privacy reasons)&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;in a second scenario, if there is no internal DNS i would encourage dns-over-tls/https as this provides more privacy&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;from the firewall you can ssl decrypt to still look inside and make sure there are not threats, but an outside listener should not be able to pick up on my dns traffic&lt;/P&gt;</description>
      <pubDate>Mon, 30 Mar 2020 13:17:27 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/blocking-dns-over-https/m-p/319377#M81908</guid>
      <dc:creator>reaper</dc:creator>
      <dc:date>2020-03-30T13:17:27Z</dc:date>
    </item>
    <item>
      <title>Re: Blocking DNS-over-https</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/blocking-dns-over-https/m-p/319383#M81910</link>
      <description>&lt;P&gt;&lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/7608"&gt;@reaper&lt;/a&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I agree your assessment. I'm all for encrypted dns, but I want all my dns requests coming from my internal dns servers, as you stated.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;However, I thought dns-over-https uses certificate pinning, which would not allow it to be decrypted?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 30 Mar 2020 13:40:07 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/blocking-dns-over-https/m-p/319383#M81910</guid>
      <dc:creator>ce1028</dc:creator>
      <dc:date>2020-03-30T13:40:07Z</dc:date>
    </item>
    <item>
      <title>Re: Blocking DNS-over-https</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/blocking-dns-over-https/m-p/319389#M81911</link>
      <description>&lt;P&gt;&lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/71649"&gt;@ce1028&lt;/a&gt;&amp;nbsp; I thought pinning was by choice&lt;/P&gt;</description>
      <pubDate>Mon, 30 Mar 2020 14:11:02 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/blocking-dns-over-https/m-p/319389#M81911</guid>
      <dc:creator>reaper</dc:creator>
      <dc:date>2020-03-30T14:11:02Z</dc:date>
    </item>
    <item>
      <title>Re: Blocking DNS-over-https</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/blocking-dns-over-https/m-p/512262#M106445</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;
&lt;P&gt;I have tow cases, one we can decrypt the traffic and this is which is possible to allow secured DNS.&lt;/P&gt;
&lt;P&gt;my second case in another network with no decryption applied "network requirements", here should I should I block the DNS_Over_https, and allow only benign DNS traffic to inhouse DNS server?&lt;/P&gt;
&lt;P&gt;Notice:&lt;/P&gt;
&lt;P&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;even without decryption rule, how possible to the firewall to read into the ssl traffic and discover the DNS_over_https?&lt;/P&gt;
&lt;P&gt;Thank you&lt;/P&gt;</description>
      <pubDate>Thu, 18 Aug 2022 12:25:49 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/blocking-dns-over-https/m-p/512262#M106445</guid>
      <dc:creator>MRamadanAHafiez</dc:creator>
      <dc:date>2022-08-18T12:25:49Z</dc:date>
    </item>
  </channel>
</rss>

