<?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 ISE 2.1 Changing FQDN in Network Access Control</title>
    <link>https://community.cisco.com/t5/network-access-control/ise-2-1-changing-fqdn/m-p/2955501#M38560</link>
    <description>&lt;P&gt;Is there a way to change the fqdn w/o needing to re-configure ISE from scratch?&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;I have a 2-node deployment.&amp;nbsp; The domain is changing - so I have a new wildcard cert for the new domain, but the server's current fqdn won't work w/ the new cert.&lt;/P&gt;</description>
    <pubDate>Mon, 11 Mar 2019 07:01:54 GMT</pubDate>
    <dc:creator>moody</dc:creator>
    <dc:date>2019-03-11T07:01:54Z</dc:date>
    <item>
      <title>ISE 2.1 Changing FQDN</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-2-1-changing-fqdn/m-p/2955501#M38560</link>
      <description>&lt;P&gt;Is there a way to change the fqdn w/o needing to re-configure ISE from scratch?&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;I have a 2-node deployment.&amp;nbsp; The domain is changing - so I have a new wildcard cert for the new domain, but the server's current fqdn won't work w/ the new cert.&lt;/P&gt;</description>
      <pubDate>Mon, 11 Mar 2019 07:01:54 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-2-1-changing-fqdn/m-p/2955501#M38560</guid>
      <dc:creator>moody</dc:creator>
      <dc:date>2019-03-11T07:01:54Z</dc:date>
    </item>
    <item>
      <title>Hi Moody,</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-2-1-changing-fqdn/m-p/2955502#M38564</link>
      <description>&lt;P&gt;Hi Moody,&lt;/P&gt;
&lt;P&gt;Domain name can be changes using below command.&lt;/P&gt;
&lt;P&gt;ISE3395/admin(config)# ip domain-name ?&lt;BR /&gt; &amp;lt;WORD&amp;gt; DNS search domain name (Max Size - 64)&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;If you update the domain name for the Cisco ISE server with this command, it displays the following warning message:&lt;/SPAN&gt;&lt;/P&gt;
&lt;PRE class="codeblock prettyprint"&gt;Warning: Updating the domain name will cause any certificate using the old
domain name to become invalid. Therefore, a new self-signed certificate using the new domain 
name will be generated now for use with HTTPs/EAP.  If CA-signed certificates were used on this
node, please import them with the correct domain name. In addition, if this ISE node will be 
joining a new Active Directory domain, please leave your current Active Directory domain before 
proceeding.&lt;/PRE&gt;
&lt;P&gt;http://www.cisco.com/c/en/us/td/docs/security/ise/2-1/cli_ref_guide/b_ise_CLIReferenceGuide_21/b_ise_CLIReferenceGuide_21_chapter_011.html#ID-1364-0000064d&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;Prior to this change:&lt;/P&gt;
&lt;P&gt;1. Disjoin the ISE nodes from the domain&lt;/P&gt;
&lt;P&gt;2. Ensure that their computer name is removed from AD&lt;/P&gt;
&lt;P&gt;3. &amp;nbsp;Update DNS records&lt;/P&gt;
&lt;P&gt;4. Ensure that DNS records have replicated&lt;/P&gt;
&lt;P&gt;5. Change names on ISE&lt;/P&gt;
&lt;P&gt;6. Join nodes to the &amp;nbsp;new domain.&lt;/P&gt;
&lt;P&gt;Hope this helps!!!!&lt;/P&gt;
&lt;P&gt;Regards&lt;/P&gt;
&lt;P&gt;Gagan&lt;/P&gt;</description>
      <pubDate>Fri, 26 Aug 2016 21:58:06 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-2-1-changing-fqdn/m-p/2955502#M38564</guid>
      <dc:creator>Gagandeep Singh</dc:creator>
      <dc:date>2016-08-26T21:58:06Z</dc:date>
    </item>
    <item>
      <title>Hi Moody,</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-2-1-changing-fqdn/m-p/2955503#M38567</link>
      <description>&lt;P&gt;&lt;SPAN&gt;Hi Moody,&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;Any queries!!!&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;Regards&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;Gagan&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;PS: please rate if it helps&lt;/P&gt;</description>
      <pubDate>Thu, 08 Sep 2016 18:43:21 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-2-1-changing-fqdn/m-p/2955503#M38567</guid>
      <dc:creator>Gagandeep Singh</dc:creator>
      <dc:date>2016-09-08T18:43:21Z</dc:date>
    </item>
    <item>
      <title>Thanks Gagan -</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-2-1-changing-fqdn/m-p/2955504#M38571</link>
      <description>&lt;P&gt;Thanks Gagan -&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;You were right w/ your steps to make the change.&amp;nbsp; I guess the real hurdle for us was getting the certificate changed.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;Thanks again - huge help!&lt;/P&gt;</description>
      <pubDate>Thu, 08 Sep 2016 20:52:27 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-2-1-changing-fqdn/m-p/2955504#M38571</guid>
      <dc:creator>moody</dc:creator>
      <dc:date>2016-09-08T20:52:27Z</dc:date>
    </item>
  </channel>
</rss>

