<?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: ASA FQDN Objects in Expedition Discussions</title>
    <link>https://live.paloaltonetworks.com/t5/expedition-discussions/asa-fqdn-objects/m-p/290105#M2024</link>
    <description>&lt;P&gt;This is not supported today, as we do not do the resolution of the FQDNs when we do the auto-zoning.&lt;/P&gt;</description>
    <pubDate>Thu, 26 Sep 2019 08:38:19 GMT</pubDate>
    <dc:creator>dgildelaig</dc:creator>
    <dc:date>2019-09-26T08:38:19Z</dc:date>
    <item>
      <title>ASA FQDN Objects</title>
      <link>https://live.paloaltonetworks.com/t5/expedition-discussions/asa-fqdn-objects/m-p/289982#M2023</link>
      <description>&lt;P&gt;How does Expedition handle FWDN objects for zone mapping in the security policy from an ASA config migration? In the process of an ASA migration that has FQDN objects but the zones in the securiy policy migrated incorrectly.&lt;/P&gt;</description>
      <pubDate>Wed, 25 Sep 2019 14:18:48 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/expedition-discussions/asa-fqdn-objects/m-p/289982#M2023</guid>
      <dc:creator>Gene_Barden</dc:creator>
      <dc:date>2019-09-25T14:18:48Z</dc:date>
    </item>
    <item>
      <title>Re: ASA FQDN Objects</title>
      <link>https://live.paloaltonetworks.com/t5/expedition-discussions/asa-fqdn-objects/m-p/290105#M2024</link>
      <description>&lt;P&gt;This is not supported today, as we do not do the resolution of the FQDNs when we do the auto-zoning.&lt;/P&gt;</description>
      <pubDate>Thu, 26 Sep 2019 08:38:19 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/expedition-discussions/asa-fqdn-objects/m-p/290105#M2024</guid>
      <dc:creator>dgildelaig</dc:creator>
      <dc:date>2019-09-26T08:38:19Z</dc:date>
    </item>
  </channel>
</rss>

