<?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 DNS Servers Failure in Next-Generation Firewall Discussions</title>
    <link>https://live.paloaltonetworks.com/t5/next-generation-firewall/dns-servers-failure/m-p/1231971#M5997</link>
    <description>&lt;P data-start="63" data-end="226"&gt;In the Palo Alto firewall, we are &lt;STRONG data-start="97" data-end="132"&gt;unable to reach the DNS servers&lt;/STRONG&gt;. These servers are in the cloud and act as &lt;STRONG data-start="176" data-end="223"&gt;proxy servers as well as domain controllers&lt;/STRONG&gt;.&lt;/P&gt;
&lt;P data-start="228" data-end="368"&gt;From our VMs, we are &lt;STRONG data-start="249" data-end="290"&gt;able to ping the DNS IPs successfully&lt;/STRONG&gt;, but in the &lt;STRONG data-start="303" data-end="328"&gt;firewall session logs&lt;/STRONG&gt;, it shows &lt;STRONG data-start="339" data-end="366"&gt;"resource unavailable."&lt;/STRONG&gt;&lt;/P&gt;
&lt;P data-start="370" data-end="525"&gt;Note that the &lt;STRONG data-start="384" data-end="447"&gt;same configuration is working on another Palo Alto firewall&lt;/STRONG&gt;, where it is able to reach the DNS servers from the assets without any issue.&lt;/P&gt;</description>
    <pubDate>Tue, 17 Jun 2025 21:41:30 GMT</pubDate>
    <dc:creator>pr45031</dc:creator>
    <dc:date>2025-06-17T21:41:30Z</dc:date>
    <item>
      <title>DNS Servers Failure</title>
      <link>https://live.paloaltonetworks.com/t5/next-generation-firewall/dns-servers-failure/m-p/1231971#M5997</link>
      <description>&lt;P data-start="63" data-end="226"&gt;In the Palo Alto firewall, we are &lt;STRONG data-start="97" data-end="132"&gt;unable to reach the DNS servers&lt;/STRONG&gt;. These servers are in the cloud and act as &lt;STRONG data-start="176" data-end="223"&gt;proxy servers as well as domain controllers&lt;/STRONG&gt;.&lt;/P&gt;
&lt;P data-start="228" data-end="368"&gt;From our VMs, we are &lt;STRONG data-start="249" data-end="290"&gt;able to ping the DNS IPs successfully&lt;/STRONG&gt;, but in the &lt;STRONG data-start="303" data-end="328"&gt;firewall session logs&lt;/STRONG&gt;, it shows &lt;STRONG data-start="339" data-end="366"&gt;"resource unavailable."&lt;/STRONG&gt;&lt;/P&gt;
&lt;P data-start="370" data-end="525"&gt;Note that the &lt;STRONG data-start="384" data-end="447"&gt;same configuration is working on another Palo Alto firewall&lt;/STRONG&gt;, where it is able to reach the DNS servers from the assets without any issue.&lt;/P&gt;</description>
      <pubDate>Tue, 17 Jun 2025 21:41:30 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/next-generation-firewall/dns-servers-failure/m-p/1231971#M5997</guid>
      <dc:creator>pr45031</dc:creator>
      <dc:date>2025-06-17T21:41:30Z</dc:date>
    </item>
    <item>
      <title>Re: DNS Servers Failure</title>
      <link>https://live.paloaltonetworks.com/t5/next-generation-firewall/dns-servers-failure/m-p/1232163#M6002</link>
      <description>&lt;P&gt;Try to create an application override for this traffic, that should work! &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt;&lt;/P&gt;</description>
      <pubDate>Fri, 20 Jun 2025 02:53:26 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/next-generation-firewall/dns-servers-failure/m-p/1232163#M6002</guid>
      <dc:creator>jfernandez1</dc:creator>
      <dc:date>2025-06-20T02:53:26Z</dc:date>
    </item>
  </channel>
</rss>

