<?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: SITE to SITE Tunnel with FQDN  in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/site-to-site-tunnel-with-fqdn/m-p/1266530#M858537</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I agree, but that's the only way an ASA can resolve names (that I know of).&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 21 Jul 2009 14:25:23 GMT</pubDate>
    <dc:creator>Collin Clark</dc:creator>
    <dc:date>2009-07-21T14:25:23Z</dc:date>
    <item>
      <title>SITE to SITE Tunnel with FQDN</title>
      <link>https://community.cisco.com/t5/network-security/site-to-site-tunnel-with-fqdn/m-p/1266527#M858534</link>
      <description>&lt;P&gt;Hi &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I want LAN to LAN tunnel between ASA and 1800 with FQDN i.e peer=ccde.vpn.com for 1800 and support.vpn.com for ASA rather than using peer ip addresses in 'set peer .. ".Is this possible to use FQDN for tunnel peers ratehr than ip addresses ?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;</description>
      <pubDate>Mon, 11 Mar 2019 15:57:07 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/site-to-site-tunnel-with-fqdn/m-p/1266527#M858534</guid>
      <dc:creator>CCDECCDE9</dc:creator>
      <dc:date>2019-03-11T15:57:07Z</dc:date>
    </item>
    <item>
      <title>Re: SITE to SITE Tunnel with FQDN</title>
      <link>https://community.cisco.com/t5/network-security/site-to-site-tunnel-with-fqdn/m-p/1266528#M858535</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Yes it's possible but there are a couple of caveats. The name must be resolvable and the ASA can not use DNS so you will need to use a static name command (kind of defeats the purpose of using a name). Other than set set the peer to the name instead of the IP. You will also have to set the identity to hostname under your isakmp profile.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hope that helps.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 20 Jul 2009 18:22:04 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/site-to-site-tunnel-with-fqdn/m-p/1266528#M858535</guid>
      <dc:creator>Collin Clark</dc:creator>
      <dc:date>2009-07-20T18:22:04Z</dc:date>
    </item>
    <item>
      <title>Re: SITE to SITE Tunnel with FQDN</title>
      <link>https://community.cisco.com/t5/network-security/site-to-site-tunnel-with-fqdn/m-p/1266529#M858536</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Collin&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;i am looking for the name  to be resolved over an internet if my peer is your router at your location then I have to put colin.vpn.com and I have no clue what ip it has and it is possible they may change the ip from time to time...so static name command doesn't really help&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 21 Jul 2009 14:18:49 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/site-to-site-tunnel-with-fqdn/m-p/1266529#M858536</guid>
      <dc:creator>CCDECCDE9</dc:creator>
      <dc:date>2009-07-21T14:18:49Z</dc:date>
    </item>
    <item>
      <title>Re: SITE to SITE Tunnel with FQDN</title>
      <link>https://community.cisco.com/t5/network-security/site-to-site-tunnel-with-fqdn/m-p/1266530#M858537</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I agree, but that's the only way an ASA can resolve names (that I know of).&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 21 Jul 2009 14:25:23 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/site-to-site-tunnel-with-fqdn/m-p/1266530#M858537</guid>
      <dc:creator>Collin Clark</dc:creator>
      <dc:date>2009-07-21T14:25:23Z</dc:date>
    </item>
    <item>
      <title>Re: SITE to SITE Tunnel with FQDN</title>
      <link>https://community.cisco.com/t5/network-security/site-to-site-tunnel-with-fqdn/m-p/1266531#M858538</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I just ran across something-&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;dns domain-lookup inside&lt;/P&gt;&lt;P&gt;dns server-group DefaultDNS&lt;/P&gt;&lt;P&gt; name-server 10.101.1.50&lt;/P&gt;&lt;P&gt; name-server 10.101.1.53&lt;/P&gt;&lt;P&gt; domain-name mylocal.lan&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Looks like it can do DNS.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 21 Jul 2009 16:05:24 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/site-to-site-tunnel-with-fqdn/m-p/1266531#M858538</guid>
      <dc:creator>Collin Clark</dc:creator>
      <dc:date>2009-07-21T16:05:24Z</dc:date>
    </item>
  </channel>
</rss>

