<?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: Identifying FQDN object addresses in log files in General Topics</title>
    <link>https://live.paloaltonetworks.com/t5/general-topics/identifying-fqdn-object-addresses-in-log-files/m-p/9207#M6734</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&lt;BR /&gt;Thanks for the feedback akawimandan.&amp;nbsp;&amp;nbsp; If we created a second rule for fqdn objects&amp;nbsp; being blocked we would still have to the problem of identifying the defined host.&amp;nbsp; I did the fqdn show and so far I have 85 entries and growing.&amp;nbsp;&amp;nbsp; After a bit of digging I might use a program called&amp;nbsp;&amp;nbsp;&amp;nbsp; &lt;A href="http://www.nirsoft.net/utils/fastresolver.html" title="http://www.nirsoft.net/utils/fastresolver.html"&gt;FastResolver - Host Names/IP Addresses/MAC Address Scanner&lt;/A&gt; which can do the DNS resolutions and then easity sort the results by IP order for easy lookup.&amp;nbsp; Your feedback and attached post showed me that there is no easy fix so I had to dig deeper. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks - Phil&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 15 Mar 2013 00:28:00 GMT</pubDate>
    <dc:creator>HITSSEC</dc:creator>
    <dc:date>2013-03-15T00:28:00Z</dc:date>
    <item>
      <title>Identifying FQDN object addresses in log files</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/identifying-fqdn-object-addresses-in-log-files/m-p/9205#M6732</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;We are using FQDN objects and network objects with a traditional IP address in rules to block traffic. How do you easily determine the associated object when all you see are IP addresses in the logs. When looking at the logs and resolving host names, the defined name appears for ip addressed objects but the dns reverse lookup value appears for the FQDN defined object not the FQDN defined name.&amp;nbsp;&amp;nbsp; It is useful when you have comments in the decription field (used to provide background info as to why we are blocking the destination)&amp;nbsp; Any suggestions would be helpful.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 13 Mar 2013 22:14:51 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/identifying-fqdn-object-addresses-in-log-files/m-p/9205#M6732</guid>
      <dc:creator>HITSSEC</dc:creator>
      <dc:date>2013-03-13T22:14:51Z</dc:date>
    </item>
    <item>
      <title>Re: Identifying FQDN object addresses in log files</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/identifying-fqdn-object-addresses-in-log-files/m-p/9206#M6733</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Logs wont show up the Object name.&lt;/P&gt;&lt;P&gt;You can check the FQDN related deatils using CLI command:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;gt; &lt;STRONG&gt;request system fqdn show&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;FQDN Table : Last Request time Thu Mar 14 00:34:58 2013&lt;/P&gt;&lt;P&gt;--------------------------------------------------------------------------------&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; IP Address&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Remaining TTL&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Secs Since Refreshed&lt;/P&gt;&lt;P&gt;--------------------------------------------------------------------------------&lt;/P&gt;&lt;P&gt;VSYS&amp;nbsp; : vsys1&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;www.google.com&amp;nbsp; (Objectname &lt;STRONG&gt;test&lt;/STRONG&gt;&lt;span class="lia-unicode-emoji" title=":disappointed_face:"&gt;😞&lt;/span&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp; 2001:4860:4002:801:0:0:0:1013&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 49&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 12&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 74.125.227.144&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 49&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 12&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 74.125.227.145&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 49&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 12&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 74.125.227.146&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 49&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 12&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 74.125.227.147&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 49&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 12&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 74.125.227.148&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 49&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 12&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;VSYS&amp;nbsp; : shared&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;"&lt;SPAN style="color: #000000; font-family: Arial, Helvetica, sans-serif; font-size: 12px; background-color: #ffffff;"&gt;Unfortunately we can only show traffic logs by IP addresses. Basically when we use FQDN in address objects, the PA device will resolve the IPs for those objects and will use that in the policy. Hence you will always see traffic logs showing IP address. However, you can perhaps configure rules with just one specific FQDN as the source or destination. Then you can to use rule name with FQDN name to be able to track in the traffic log.&lt;/SPAN&gt;" -rkim&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;ref:&lt;A __default_attr="10433" __jive_macro_name="message" class="jive_macro jive_macro_message" href="https://live.paloaltonetworks.com/"&gt;&lt;/A&gt;&lt;/P&gt;&lt;P&gt;-AMeya&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 14 Mar 2013 07:36:35 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/identifying-fqdn-object-addresses-in-log-files/m-p/9206#M6733</guid>
      <dc:creator>UhMayYeah</dc:creator>
      <dc:date>2013-03-14T07:36:35Z</dc:date>
    </item>
    <item>
      <title>Re: Identifying FQDN object addresses in log files</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/identifying-fqdn-object-addresses-in-log-files/m-p/9207#M6734</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&lt;BR /&gt;Thanks for the feedback akawimandan.&amp;nbsp;&amp;nbsp; If we created a second rule for fqdn objects&amp;nbsp; being blocked we would still have to the problem of identifying the defined host.&amp;nbsp; I did the fqdn show and so far I have 85 entries and growing.&amp;nbsp;&amp;nbsp; After a bit of digging I might use a program called&amp;nbsp;&amp;nbsp;&amp;nbsp; &lt;A href="http://www.nirsoft.net/utils/fastresolver.html" title="http://www.nirsoft.net/utils/fastresolver.html"&gt;FastResolver - Host Names/IP Addresses/MAC Address Scanner&lt;/A&gt; which can do the DNS resolutions and then easity sort the results by IP order for easy lookup.&amp;nbsp; Your feedback and attached post showed me that there is no easy fix so I had to dig deeper. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks - Phil&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 15 Mar 2013 00:28:00 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/identifying-fqdn-object-addresses-in-log-files/m-p/9207#M6734</guid>
      <dc:creator>HITSSEC</dc:creator>
      <dc:date>2013-03-15T00:28:00Z</dc:date>
    </item>
  </channel>
</rss>

