<?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: DNS logs in Advanced Threat Prevention Discussions</title>
    <link>https://live.paloaltonetworks.com/t5/advanced-threat-prevention/dns-logs/m-p/272795#M594</link>
    <description>&lt;P&gt;Technically, you could create a custom vulnerability that would match "normal" DNS traffic, set it to Alert for the action and set packet capturing to on. Unless you have plenty of resource overhead available to use on your PA I'm guessing this could be a bad idea for that much packet capturing just the same. It would fill up threat log quota or &lt;SPAN&gt;Extended Threat Pcaps quotea&amp;nbsp;&lt;/SPAN&gt;much more rapidly. In the logging then you would get a request source and destination just having to open the PCAP to get the domain record that was requested.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;It would be great if there were just a DNS lookup log with the requestor IP included. Perhaps on your DNS server this is done and you can limit DNS lookups to just your DNS server(s) so everyone would need to be pointed there.&lt;/P&gt;</description>
    <pubDate>Mon, 24 Jun 2019 21:26:09 GMT</pubDate>
    <dc:creator>bspilde</dc:creator>
    <dc:date>2019-06-24T21:26:09Z</dc:date>
    <item>
      <title>DNS logs</title>
      <link>https://live.paloaltonetworks.com/t5/advanced-threat-prevention/dns-logs/m-p/246511#M485</link>
      <description>&lt;P&gt;Is there a way to view and/or log dns queries and responses (outside of anti-spyware rules)? The passive DNS telemetry configuration seems to do what we want but those fqdn to IP mappings are sent to Palo and it doesn't appear that we can view what fqdns resolve to what IPs in the logs. This doesn't appear to be a feature in the dns proxy object either? Is there anything with PAN-OS that supports this? For all queries not just malicious ones.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 17 Jan 2019 16:15:54 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/advanced-threat-prevention/dns-logs/m-p/246511#M485</guid>
      <dc:creator>mpochan</dc:creator>
      <dc:date>2019-01-17T16:15:54Z</dc:date>
    </item>
    <item>
      <title>Re: DNS logs</title>
      <link>https://live.paloaltonetworks.com/t5/advanced-threat-prevention/dns-logs/m-p/246523#M486</link>
      <description>&lt;P&gt;You can setup a continuos packet capture in the firewall for protocol 17 (udp) and destination port 53, and then check the packet capture when you need this information. If you have excessive DNS traffic through your firewall this can cause increased dataplane CPU utilization, so be careful.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;For the DNS Proxy feature in the firewall you can check its cache from the CLI:&lt;BR /&gt;&lt;BR /&gt;&amp;gt; show dns-proxy cache all | match&amp;nbsp;&amp;lt;fqdn&amp;gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;OR&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;gt; show dns-proxy cache filter type RR_A all FQDN&amp;nbsp;&amp;lt;fqdn&amp;gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 17 Jan 2019 19:06:06 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/advanced-threat-prevention/dns-logs/m-p/246523#M486</guid>
      <dc:creator>mivaldi</dc:creator>
      <dc:date>2019-01-17T19:06:06Z</dc:date>
    </item>
    <item>
      <title>Re: DNS logs</title>
      <link>https://live.paloaltonetworks.com/t5/advanced-threat-prevention/dns-logs/m-p/272795#M594</link>
      <description>&lt;P&gt;Technically, you could create a custom vulnerability that would match "normal" DNS traffic, set it to Alert for the action and set packet capturing to on. Unless you have plenty of resource overhead available to use on your PA I'm guessing this could be a bad idea for that much packet capturing just the same. It would fill up threat log quota or &lt;SPAN&gt;Extended Threat Pcaps quotea&amp;nbsp;&lt;/SPAN&gt;much more rapidly. In the logging then you would get a request source and destination just having to open the PCAP to get the domain record that was requested.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;It would be great if there were just a DNS lookup log with the requestor IP included. Perhaps on your DNS server this is done and you can limit DNS lookups to just your DNS server(s) so everyone would need to be pointed there.&lt;/P&gt;</description>
      <pubDate>Mon, 24 Jun 2019 21:26:09 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/advanced-threat-prevention/dns-logs/m-p/272795#M594</guid>
      <dc:creator>bspilde</dc:creator>
      <dc:date>2019-06-24T21:26:09Z</dc:date>
    </item>
  </channel>
</rss>

