<?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 On which appliance, you are in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/objects-with-fqdn/m-p/2629604#M1027637</link>
    <description>&lt;P class="p1"&gt;&lt;SPAN class="s1"&gt;On which appliance, you are asking to configure the FQDN.&lt;/SPAN&gt;&lt;/P&gt;
&lt;P class="p1"&gt;&lt;SPAN class="s1"&gt;If this is ASA, yes you can do it. Please have a look on this article&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P class="p1"&gt;&lt;SPAN class="s1"&gt;https://supportforums.cisco.com/document/66011/using-hostnames-dns-access-lists-configuration-steps-caveats-and-troubleshooting&lt;/SPAN&gt;&lt;/P&gt;
&lt;P class="p1"&gt;&lt;SPAN class="s1"&gt;Firepower/Sourcefire supports FQDN for URL filtering purpose. You can also configure FQDN in Security Intelligence's blacklisting as to block the IP address based upon domains but port based filtering with FQDN is not possible. &lt;/SPAN&gt;&lt;/P&gt;</description>
    <pubDate>Tue, 19 Jan 2016 05:31:24 GMT</pubDate>
    <dc:creator>Sunil Kumar</dc:creator>
    <dc:date>2016-01-19T05:31:24Z</dc:date>
    <item>
      <title>Objects with FQDN</title>
      <link>https://community.cisco.com/t5/network-security/objects-with-fqdn/m-p/2629602#M1027635</link>
      <description>&lt;P&gt;Hi!&lt;/P&gt;&lt;P&gt;is it possible to create an object with fqdn instead of ips?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;thanks&lt;/P&gt;</description>
      <pubDate>Tue, 12 Mar 2019 12:39:02 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/objects-with-fqdn/m-p/2629602#M1027635</guid>
      <dc:creator>WebOps eDreams</dc:creator>
      <dc:date>2019-03-12T12:39:02Z</dc:date>
    </item>
    <item>
      <title>Hi, </title>
      <link>https://community.cisco.com/t5/network-security/objects-with-fqdn/m-p/2629603#M1027636</link>
      <description>&lt;P&gt;Hi,&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;Yes, you can add FQDN under Object management -&amp;gt;URL.&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;Hope it helps.&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;Thanks,&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;Ankita&lt;/P&gt;</description>
      <pubDate>Mon, 18 Jan 2016 16:33:55 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/objects-with-fqdn/m-p/2629603#M1027636</guid>
      <dc:creator>ankojha</dc:creator>
      <dc:date>2016-01-18T16:33:55Z</dc:date>
    </item>
    <item>
      <title>On which appliance, you are</title>
      <link>https://community.cisco.com/t5/network-security/objects-with-fqdn/m-p/2629604#M1027637</link>
      <description>&lt;P class="p1"&gt;&lt;SPAN class="s1"&gt;On which appliance, you are asking to configure the FQDN.&lt;/SPAN&gt;&lt;/P&gt;
&lt;P class="p1"&gt;&lt;SPAN class="s1"&gt;If this is ASA, yes you can do it. Please have a look on this article&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P class="p1"&gt;&lt;SPAN class="s1"&gt;https://supportforums.cisco.com/document/66011/using-hostnames-dns-access-lists-configuration-steps-caveats-and-troubleshooting&lt;/SPAN&gt;&lt;/P&gt;
&lt;P class="p1"&gt;&lt;SPAN class="s1"&gt;Firepower/Sourcefire supports FQDN for URL filtering purpose. You can also configure FQDN in Security Intelligence's blacklisting as to block the IP address based upon domains but port based filtering with FQDN is not possible. &lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 19 Jan 2016 05:31:24 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/objects-with-fqdn/m-p/2629604#M1027637</guid>
      <dc:creator>Sunil Kumar</dc:creator>
      <dc:date>2016-01-19T05:31:24Z</dc:date>
    </item>
    <item>
      <title>Hi Sunil!</title>
      <link>https://community.cisco.com/t5/network-security/objects-with-fqdn/m-p/2629605#M1027638</link>
      <description>&lt;P&gt;Hi Sunil!&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;Actually thats what i was trying to do fqdn with port based filtering or application detection.&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;Basically we have several server/resources in our internal networks which we access by using fqdn (using internal dns) and the idea is to create acls but with diferent ports than 80 /443.&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;We found no way to accomplish this; only by using static ips but this is not a 'nice' way to do it.&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 19 Jan 2016 09:21:03 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/objects-with-fqdn/m-p/2629605#M1027638</guid>
      <dc:creator>WebOps eDreams</dc:creator>
      <dc:date>2016-01-19T09:21:03Z</dc:date>
    </item>
    <item>
      <title>Re: Hi,</title>
      <link>https://community.cisco.com/t5/network-security/objects-with-fqdn/m-p/3200706#M1027639</link>
      <description>&lt;P&gt;But this means you need a URL License on your firepower system. Before (on ASA) there existed FQDN objects without any URL Lic. Is this correct?&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;r Johannes&lt;/P&gt;</description>
      <pubDate>Wed, 18 Oct 2017 09:18:31 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/objects-with-fqdn/m-p/3200706#M1027639</guid>
      <dc:creator>johannes88</dc:creator>
      <dc:date>2017-10-18T09:18:31Z</dc:date>
    </item>
  </channel>
</rss>

