<?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: Finding IP of threat blocked via DNS Proxy in Next-Generation Firewall Discussions</title>
    <link>https://live.paloaltonetworks.com/t5/next-generation-firewall/finding-ip-of-threat-blocked-via-dns-proxy/m-p/1236154#M6213</link>
    <description>&lt;P&gt;you can switch to DNS sinkhole instead of blocking. This will poison the malicious DNS reply with your own (or Palo's) sinkhole IP and you'll see the original client make connections to that IP as it received a DNS reply and will now try to connect to it&lt;/P&gt;</description>
    <pubDate>Mon, 18 Aug 2025 09:34:33 GMT</pubDate>
    <dc:creator>reaper</dc:creator>
    <dc:date>2025-08-18T09:34:33Z</dc:date>
    <item>
      <title>Finding IP of threat blocked via DNS Proxy</title>
      <link>https://live.paloaltonetworks.com/t5/next-generation-firewall/finding-ip-of-threat-blocked-via-dns-proxy/m-p/1235758#M6187</link>
      <description>&lt;P&gt;As our PA is configured at the moment, I see some notifications in the threat logs where a request from the Palo DNS proxy has been blocked from looking up something determined to be spyware.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I can't find a matching log anywhere to indicate the IP which made the DNS request to the Palo's DNS proxy. I'd appreciate some direction.&lt;/P&gt;
&lt;P&gt;I'm aware some privacy apps use onion, this is just a generic example from the top of my logs. Many other examples which are virtually identical but for other spyware threats, all blocked the same way with no way to track the source.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Example:&lt;/P&gt;
&lt;TABLE width="1017"&gt;
&lt;TBODY&gt;
&lt;TR&gt;
&lt;TD width="110"&gt;Receive Time&lt;/TD&gt;
&lt;TD width="64"&gt;Threat/Content Type&lt;/TD&gt;
&lt;TD width="98"&gt;Source address&lt;/TD&gt;
&lt;TD width="64"&gt;Destination address&lt;/TD&gt;
&lt;TD width="88"&gt;NAT Source IP&lt;/TD&gt;
&lt;TD width="114"&gt;NAT Destination IP&lt;/TD&gt;
&lt;TD width="72"&gt;Application&lt;/TD&gt;
&lt;TD width="64"&gt;Source Zone&lt;/TD&gt;
&lt;TD width="64"&gt;Destination Zone&lt;/TD&gt;
&lt;TD width="130"&gt;URL/Filename&lt;/TD&gt;
&lt;TD width="149"&gt;Threat/Content Name&lt;/TD&gt;
&lt;/TR&gt;
&lt;TR&gt;
&lt;TD&gt;11/08/2025 15:18&lt;/TD&gt;
&lt;TD&gt;spyware&lt;/TD&gt;
&lt;TD&gt;[DNS-Proxy IP]&lt;/TD&gt;
&lt;TD&gt;1.0.0.1&lt;/TD&gt;
&lt;TD&gt;[external IP]&lt;/TD&gt;
&lt;TD&gt;1.0.0.1&lt;/TD&gt;
&lt;TD&gt;dns-base&lt;/TD&gt;
&lt;TD&gt;[guest]&lt;/TD&gt;
&lt;TD&gt;untrust&lt;/TD&gt;
&lt;TD&gt;google.com.onion&lt;/TD&gt;
&lt;TD&gt;Proxy:onion(109010004)&lt;/TD&gt;
&lt;/TR&gt;
&lt;TR&gt;
&lt;TD&gt;11/08/2025 15:18&lt;/TD&gt;
&lt;TD&gt;spyware&lt;/TD&gt;
&lt;TD&gt;[DNS-Proxy IP]&lt;/TD&gt;
&lt;TD&gt;1.0.0.1&lt;/TD&gt;
&lt;TD&gt;[external IP]&lt;/TD&gt;
&lt;TD&gt;1.0.0.1&lt;/TD&gt;
&lt;TD&gt;dns-base&lt;/TD&gt;
&lt;TD&gt;[guest]&lt;/TD&gt;
&lt;TD&gt;untrust&lt;/TD&gt;
&lt;TD&gt;google.com.onion&lt;/TD&gt;
&lt;TD&gt;Proxy:onion(109010004)&lt;/TD&gt;
&lt;/TR&gt;
&lt;TR&gt;
&lt;TD&gt;11/08/2025 15:17&lt;/TD&gt;
&lt;TD&gt;spyware&lt;/TD&gt;
&lt;TD&gt;[DNS-Proxy IP]&lt;/TD&gt;
&lt;TD&gt;1.0.0.1&lt;/TD&gt;
&lt;TD&gt;[external IP]&lt;/TD&gt;
&lt;TD&gt;1.0.0.1&lt;/TD&gt;
&lt;TD&gt;dns-base&lt;/TD&gt;
&lt;TD&gt;[guest]&lt;/TD&gt;
&lt;TD&gt;untrust&lt;/TD&gt;
&lt;TD&gt;google.com.onion&lt;/TD&gt;
&lt;TD&gt;Proxy:onion(109010004)&lt;/TD&gt;
&lt;/TR&gt;
&lt;/TBODY&gt;
&lt;/TABLE&gt;</description>
      <pubDate>Mon, 11 Aug 2025 06:14:21 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/next-generation-firewall/finding-ip-of-threat-blocked-via-dns-proxy/m-p/1235758#M6187</guid>
      <dc:creator>SASY-IT</dc:creator>
      <dc:date>2025-08-11T06:14:21Z</dc:date>
    </item>
    <item>
      <title>Re: Finding IP of threat blocked via DNS Proxy</title>
      <link>https://live.paloaltonetworks.com/t5/next-generation-firewall/finding-ip-of-threat-blocked-via-dns-proxy/m-p/1236154#M6213</link>
      <description>&lt;P&gt;you can switch to DNS sinkhole instead of blocking. This will poison the malicious DNS reply with your own (or Palo's) sinkhole IP and you'll see the original client make connections to that IP as it received a DNS reply and will now try to connect to it&lt;/P&gt;</description>
      <pubDate>Mon, 18 Aug 2025 09:34:33 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/next-generation-firewall/finding-ip-of-threat-blocked-via-dns-proxy/m-p/1236154#M6213</guid>
      <dc:creator>reaper</dc:creator>
      <dc:date>2025-08-18T09:34:33Z</dc:date>
    </item>
  </channel>
</rss>

