<?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: Palo alto denying the traffic randamly in Next-Generation Firewall Discussions</title>
    <link>https://live.paloaltonetworks.com/t5/next-generation-firewall/palo-alto-denying-the-traffic-randamly/m-p/508174#M196</link>
    <description>&lt;P&gt;Hi &lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/225405"&gt;@Abhishekrs987&lt;/a&gt; ,&lt;/P&gt;
&lt;P&gt;Interesting...I can see this FQDN also has very long TTL. Are you able to provide screenshot from your rule and from defailed log view (magnifing glass on the far left of the log entry) for both allowed and denied traffic. Feel free to obfuscate any sensitive information (IP addresses, source users, zone names)&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I just re-read your question - as mentioned here - &lt;A href="https://docs.paloaltonetworks.com/pan-os/9-1/pan-os-admin/monitoring/use-syslog-for-monitoring/syslog-field-descriptions/traffic-log-fields" target="_blank"&gt;https://docs.paloaltonetworks.com/pan-os/9-1/pan-os-admin/monitoring/use-syslog-for-monitoring/syslog-field-descriptions/traffic-log-fields&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;Action Source will&amp;nbsp; specificy where the final action was defined by the rule or by the application. It should be normal to see "from-application" when traffic is blocked. This is because each application definition has "deny action", which will tell the firewall how what to do when it denies the traffic. This is important, because some applications are sensitive and when connection is denied, FW needs to send TCP RST or the connection will stall on either the client or the server.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I am intersted to see the "Session End Reason" log field for both allowed and blocked traffic.&lt;/P&gt;</description>
    <pubDate>Thu, 07 Jul 2022 08:31:31 GMT</pubDate>
    <dc:creator>aleksandar.astardzhiev</dc:creator>
    <dc:date>2022-07-07T08:31:31Z</dc:date>
    <item>
      <title>Palo alto denying the traffic randamly</title>
      <link>https://live.paloaltonetworks.com/t5/next-generation-firewall/palo-alto-denying-the-traffic-randamly/m-p/507446#M188</link>
      <description>&lt;P&gt;A simple rule is created in my firewall, where the traffic is allowed from our servers to the fqdn which is reaiding in internet. Application is as any and in service 443 is allowed.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Sometimes firewall is allowing the traffic , sometimes it is denying.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;The only difference which i observed on the log is action source. If action source is from-policy traffic is allowed and if it is from-application traffic is blocked.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I tried modifying the rule by adding ssl and web-browsing, but no luck&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Please suggest here.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 30 Jun 2022 15:08:06 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/next-generation-firewall/palo-alto-denying-the-traffic-randamly/m-p/507446#M188</guid>
      <dc:creator>Abhishekrs987</dc:creator>
      <dc:date>2022-06-30T15:08:06Z</dc:date>
    </item>
    <item>
      <title>Re: Palo alto denying the traffic randamly</title>
      <link>https://live.paloaltonetworks.com/t5/next-generation-firewall/palo-alto-denying-the-traffic-randamly/m-p/507621#M189</link>
      <description>&lt;P&gt;Hi &lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/225405"&gt;@Abhishekrs987&lt;/a&gt; ,&lt;/P&gt;
&lt;P&gt;I am almost certain that the problem is caused by the FQDN object. More specifically the FQDN you are trying to reach is using DNS loadbalaning which will return differen IPs every few requests.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;What (most probably) is happening is that:&lt;/P&gt;
&lt;P&gt;- By default firewall is making DNS request every 30mins to resolve the FQDN object used in the policy. When it receive reply it will cache all the IPs and use them in the policy (for the next 30mins). After 30mins it will repeat the process and if it receives different IPs it will replace them in the allow rule.&lt;/P&gt;
&lt;P&gt;- Every time user tries to reach the FQDN it will make new DNS request (of course it will cache the reply, but untill the TTL expires).&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;One way you can try to solve this is to tell the firewall to use the TTL in the DNS response. This will have benefit for FQDNs with short TTL. The problem is it could bring additional load to the management plane (it will force the firewall to make additional DNS queries and constantly updating the policy).&lt;/P&gt;
&lt;P&gt;Unfortunately I am not sure that will help agains DNS round robin load balancing, where almost every DNS request receive different reply. I think I have seen such with some Office365 or Azure services....cannot remember specific exmaple right now.&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>Fri, 01 Jul 2022 07:42:18 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/next-generation-firewall/palo-alto-denying-the-traffic-randamly/m-p/507621#M189</guid>
      <dc:creator>aleksandar.astardzhiev</dc:creator>
      <dc:date>2022-07-01T07:42:18Z</dc:date>
    </item>
    <item>
      <title>Re: Palo alto denying the traffic randamly</title>
      <link>https://live.paloaltonetworks.com/t5/next-generation-firewall/palo-alto-denying-the-traffic-randamly/m-p/508164#M195</link>
      <description>&lt;P&gt;Hi &lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/70130"&gt;@aleksandar.astardzhiev&lt;/a&gt;&amp;nbsp;,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Thanks for the response. It is very informative.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;But the fqdn which i created is tools1.cisco.com, when i tried resolving it everytime it resolves to a single IP and even in the logs for both the deny and allow logs i am seeing same ip in the destination&amp;nbsp;&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;
&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>Thu, 07 Jul 2022 06:11:16 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/next-generation-firewall/palo-alto-denying-the-traffic-randamly/m-p/508164#M195</guid>
      <dc:creator>Abhishekrs987</dc:creator>
      <dc:date>2022-07-07T06:11:16Z</dc:date>
    </item>
    <item>
      <title>Re: Palo alto denying the traffic randamly</title>
      <link>https://live.paloaltonetworks.com/t5/next-generation-firewall/palo-alto-denying-the-traffic-randamly/m-p/508174#M196</link>
      <description>&lt;P&gt;Hi &lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/225405"&gt;@Abhishekrs987&lt;/a&gt; ,&lt;/P&gt;
&lt;P&gt;Interesting...I can see this FQDN also has very long TTL. Are you able to provide screenshot from your rule and from defailed log view (magnifing glass on the far left of the log entry) for both allowed and denied traffic. Feel free to obfuscate any sensitive information (IP addresses, source users, zone names)&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I just re-read your question - as mentioned here - &lt;A href="https://docs.paloaltonetworks.com/pan-os/9-1/pan-os-admin/monitoring/use-syslog-for-monitoring/syslog-field-descriptions/traffic-log-fields" target="_blank"&gt;https://docs.paloaltonetworks.com/pan-os/9-1/pan-os-admin/monitoring/use-syslog-for-monitoring/syslog-field-descriptions/traffic-log-fields&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;Action Source will&amp;nbsp; specificy where the final action was defined by the rule or by the application. It should be normal to see "from-application" when traffic is blocked. This is because each application definition has "deny action", which will tell the firewall how what to do when it denies the traffic. This is important, because some applications are sensitive and when connection is denied, FW needs to send TCP RST or the connection will stall on either the client or the server.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I am intersted to see the "Session End Reason" log field for both allowed and blocked traffic.&lt;/P&gt;</description>
      <pubDate>Thu, 07 Jul 2022 08:31:31 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/next-generation-firewall/palo-alto-denying-the-traffic-randamly/m-p/508174#M196</guid>
      <dc:creator>aleksandar.astardzhiev</dc:creator>
      <dc:date>2022-07-07T08:31:31Z</dc:date>
    </item>
    <item>
      <title>Re: Palo alto denying the traffic randamly</title>
      <link>https://live.paloaltonetworks.com/t5/next-generation-firewall/palo-alto-denying-the-traffic-randamly/m-p/1229447#M5905</link>
      <description>&lt;P&gt;Hi Abhishek,&lt;BR /&gt;&lt;BR /&gt;Were you able to resolve or identify the cause I am facing the same issue.&lt;/P&gt;</description>
      <pubDate>Mon, 19 May 2025 12:29:15 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/next-generation-firewall/palo-alto-denying-the-traffic-randamly/m-p/1229447#M5905</guid>
      <dc:creator>JubairJunaid</dc:creator>
      <dc:date>2025-05-19T12:29:15Z</dc:date>
    </item>
  </channel>
</rss>

