<?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: Dynamic IP lists and FQDN? in Advanced Threat Prevention Discussions</title>
    <link>https://live.paloaltonetworks.com/t5/advanced-threat-prevention/dynamic-ip-lists-and-fqdn/m-p/230868#M405</link>
    <description>&lt;P&gt;Hello Jim, I believe the following documentation should address your concerns.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;A href="https://www.paloaltonetworks.com/documentation/71/pan-os/pan-os/policy/external-dynamic-list.html" target="_blank"&gt;https://www.paloaltonetworks.com/documentation/71/pan-os/pan-os/policy/external-dynamic-list.html&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&lt;A href="https://www.paloaltonetworks.com/documentation/71/pan-os/pan-os/policy/use-an-external-dynamic-list-in-policy" target="_blank"&gt;https://www.paloaltonetworks.com/documentation/71/pan-os/pan-os/policy/use-an-external-dynamic-list-in-policy&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Note that EDLs support three types: IP Address, URL, and Domain&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I believe in your situation you would want to use a URL type EDL in a security policy rule.&amp;nbsp; Otherwise, a second option would be to create an address object group which contains multiple FQDN address objects.&lt;/P&gt;</description>
    <pubDate>Fri, 14 Sep 2018 14:54:06 GMT</pubDate>
    <dc:creator>bvandivier</dc:creator>
    <dc:date>2018-09-14T14:54:06Z</dc:date>
    <item>
      <title>Dynamic IP lists and FQDN?</title>
      <link>https://live.paloaltonetworks.com/t5/advanced-threat-prevention/dynamic-ip-lists-and-fqdn/m-p/230812#M404</link>
      <description>&lt;P&gt;The only type of external dynamic list i appear to be able to specify in my firewall policy is a dynamic IP list (not a dynamic domain list). And the formatting of such lists appears to be purely for IP addresses. So my question is, how can i specify fully qualified domain names in a dynamic list usable in a firewall policy?&lt;/P&gt;</description>
      <pubDate>Fri, 14 Sep 2018 02:44:33 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/advanced-threat-prevention/dynamic-ip-lists-and-fqdn/m-p/230812#M404</guid>
      <dc:creator>JimMcGrady</dc:creator>
      <dc:date>2018-09-14T02:44:33Z</dc:date>
    </item>
    <item>
      <title>Re: Dynamic IP lists and FQDN?</title>
      <link>https://live.paloaltonetworks.com/t5/advanced-threat-prevention/dynamic-ip-lists-and-fqdn/m-p/230868#M405</link>
      <description>&lt;P&gt;Hello Jim, I believe the following documentation should address your concerns.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;A href="https://www.paloaltonetworks.com/documentation/71/pan-os/pan-os/policy/external-dynamic-list.html" target="_blank"&gt;https://www.paloaltonetworks.com/documentation/71/pan-os/pan-os/policy/external-dynamic-list.html&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&lt;A href="https://www.paloaltonetworks.com/documentation/71/pan-os/pan-os/policy/use-an-external-dynamic-list-in-policy" target="_blank"&gt;https://www.paloaltonetworks.com/documentation/71/pan-os/pan-os/policy/use-an-external-dynamic-list-in-policy&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Note that EDLs support three types: IP Address, URL, and Domain&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I believe in your situation you would want to use a URL type EDL in a security policy rule.&amp;nbsp; Otherwise, a second option would be to create an address object group which contains multiple FQDN address objects.&lt;/P&gt;</description>
      <pubDate>Fri, 14 Sep 2018 14:54:06 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/advanced-threat-prevention/dynamic-ip-lists-and-fqdn/m-p/230868#M405</guid>
      <dc:creator>bvandivier</dc:creator>
      <dc:date>2018-09-14T14:54:06Z</dc:date>
    </item>
  </channel>
</rss>

