<?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 Finding FQDNs for blocked IP's or SSL-Inspection in Next-Generation Firewall Discussions</title>
    <link>https://live.paloaltonetworks.com/t5/next-generation-firewall/finding-fqdns-for-blocked-ip-s-or-ssl-inspection/m-p/1002711#M5364</link>
    <description>&lt;P&gt;Once a week, someone reports having issues accessing a site.&amp;nbsp; Today that issue involves a credit card processing page that is aging-out because there is no SSL inspection exception.&amp;nbsp; FW Logs of course show an IP address (no URL/FQDN), and the rule to allow access or exclude from ssl inspection requires using an FQDN.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;The page URL in address bar has been allowed and browser/dev tools/console/sources does not indicate any other place where the browser is trying to go.&amp;nbsp; I also look at OpenDNS reports to see what DNS queries the user made around the same time.&amp;nbsp; There can be 100 sites within a few seconds, so I end up doing an NSLOOKUP on each of the FQDNs in the OpenDNS report to see if the IP matches the blocked traffic in the FW.&amp;nbsp; Once I match the FQDN to the IP, I know that is the FQDN that needs to be unblocked in the FW.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;This is a very tedious process, and after spending an hour on this today, I am not able to find the right FQDN to match the IP's that are being blocked.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Does anyone have a tool or better way to locate FQDNs for blocked IP's?&amp;nbsp; If life were easy, OpenDNS (OR PALO) would record both the FQDN and the translated IP when DNS is queried&amp;nbsp; so I would not have to search for it, but alas, that doesn't seem to be a thing for any vendor, so I keep having to do these treasure hunts on a regular basis.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Any suggestions/tricks/tips would be greatly appreciated.&lt;/P&gt;</description>
    <pubDate>Fri, 10 Jan 2025 15:36:25 GMT</pubDate>
    <dc:creator>ppeeters</dc:creator>
    <dc:date>2025-01-10T15:36:25Z</dc:date>
    <item>
      <title>Finding FQDNs for blocked IP's or SSL-Inspection</title>
      <link>https://live.paloaltonetworks.com/t5/next-generation-firewall/finding-fqdns-for-blocked-ip-s-or-ssl-inspection/m-p/1002711#M5364</link>
      <description>&lt;P&gt;Once a week, someone reports having issues accessing a site.&amp;nbsp; Today that issue involves a credit card processing page that is aging-out because there is no SSL inspection exception.&amp;nbsp; FW Logs of course show an IP address (no URL/FQDN), and the rule to allow access or exclude from ssl inspection requires using an FQDN.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;The page URL in address bar has been allowed and browser/dev tools/console/sources does not indicate any other place where the browser is trying to go.&amp;nbsp; I also look at OpenDNS reports to see what DNS queries the user made around the same time.&amp;nbsp; There can be 100 sites within a few seconds, so I end up doing an NSLOOKUP on each of the FQDNs in the OpenDNS report to see if the IP matches the blocked traffic in the FW.&amp;nbsp; Once I match the FQDN to the IP, I know that is the FQDN that needs to be unblocked in the FW.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;This is a very tedious process, and after spending an hour on this today, I am not able to find the right FQDN to match the IP's that are being blocked.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Does anyone have a tool or better way to locate FQDNs for blocked IP's?&amp;nbsp; If life were easy, OpenDNS (OR PALO) would record both the FQDN and the translated IP when DNS is queried&amp;nbsp; so I would not have to search for it, but alas, that doesn't seem to be a thing for any vendor, so I keep having to do these treasure hunts on a regular basis.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Any suggestions/tricks/tips would be greatly appreciated.&lt;/P&gt;</description>
      <pubDate>Fri, 10 Jan 2025 15:36:25 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/next-generation-firewall/finding-fqdns-for-blocked-ip-s-or-ssl-inspection/m-p/1002711#M5364</guid>
      <dc:creator>ppeeters</dc:creator>
      <dc:date>2025-01-10T15:36:25Z</dc:date>
    </item>
    <item>
      <title>Re: Finding FQDNs for blocked IP's or SSL-Inspection</title>
      <link>https://live.paloaltonetworks.com/t5/next-generation-firewall/finding-fqdns-for-blocked-ip-s-or-ssl-inspection/m-p/1066318#M5378</link>
      <description>&lt;P&gt;Hello&amp;nbsp;&lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/13369"&gt;@ppeeters&lt;/a&gt;&amp;nbsp;,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;DNS Security may help, if your FQDN is somehow a possible risk domain.&lt;/P&gt;
&lt;P&gt;Maybe you can enable the logging (once your firewall is fixed for CVE-20243393) and monitor the threat logs for input.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Otherwise, you can let a capture running on DNS traffic from a computer and check directly in the capture when needed.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Similar to that, you can set up a DNS proxy on the firewall, so you can check on the DNS proxy cache on the firewall.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Olivier&lt;/P&gt;</description>
      <pubDate>Tue, 14 Jan 2025 02:31:46 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/next-generation-firewall/finding-fqdns-for-blocked-ip-s-or-ssl-inspection/m-p/1066318#M5378</guid>
      <dc:creator>ozheng</dc:creator>
      <dc:date>2025-01-14T02:31:46Z</dc:date>
    </item>
  </channel>
</rss>

