<?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: DNS resolution issue with ISE in Network Access Control</title>
    <link>https://community.cisco.com/t5/network-access-control/dns-resolution-issue-with-ise/m-p/5223316#M593144</link>
    <description>&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;- It's rather unclear what the real or effective problem is ; correcting a domain name and hostname is not related to dns lookup(s) ; you may want to elaborate ,&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;M.&lt;/P&gt;</description>
    <pubDate>Tue, 12 Nov 2024 16:11:29 GMT</pubDate>
    <dc:creator>Mark Elsen</dc:creator>
    <dc:date>2024-11-12T16:11:29Z</dc:date>
    <item>
      <title>DNS resolution issue with ISE</title>
      <link>https://community.cisco.com/t5/network-access-control/dns-resolution-issue-with-ise/m-p/5223310#M593143</link>
      <description>&lt;P&gt;Incorrect hostname and domain name on CLI preventing DNS lookup from working. Corrected the domain name and hostname but health checks within GUI are still showing failed and the old hostname and domain details...&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 12 Nov 2024 16:04:38 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/dns-resolution-issue-with-ise/m-p/5223310#M593143</guid>
      <dc:creator>NetworkMonkey101</dc:creator>
      <dc:date>2024-11-12T16:04:38Z</dc:date>
    </item>
    <item>
      <title>Re: DNS resolution issue with ISE</title>
      <link>https://community.cisco.com/t5/network-access-control/dns-resolution-issue-with-ise/m-p/5223316#M593144</link>
      <description>&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;- It's rather unclear what the real or effective problem is ; correcting a domain name and hostname is not related to dns lookup(s) ; you may want to elaborate ,&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;M.&lt;/P&gt;</description>
      <pubDate>Tue, 12 Nov 2024 16:11:29 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/dns-resolution-issue-with-ise/m-p/5223316#M593144</guid>
      <dc:creator>Mark Elsen</dc:creator>
      <dc:date>2024-11-12T16:11:29Z</dc:date>
    </item>
    <item>
      <title>Re: DNS resolution issue with ISE</title>
      <link>https://community.cisco.com/t5/network-access-control/dns-resolution-issue-with-ise/m-p/5223320#M593145</link>
      <description>&lt;P&gt;I have incorrectly set the domain name to say domain2.net instead of domain.1net. I have amended the domain within the CLI but the health checks are still using domain2.net&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="NetworkMonkey101_0-1731428160803.png" style="width: 400px;"&gt;&lt;img src="https://community.cisco.com/t5/image/serverpage/image-id/233732i9B1CCB626BF6EDBB/image-size/medium?v=v2&amp;amp;px=400" role="button" title="NetworkMonkey101_0-1731428160803.png" alt="NetworkMonkey101_0-1731428160803.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;Same as the for hostname was set to P1- but has been changed to P2- and still using the old hostname in the DNS checks..&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="NetworkMonkey101_1-1731428341538.png" style="width: 400px;"&gt;&lt;img src="https://community.cisco.com/t5/image/serverpage/image-id/233733i0B3E6C457200D9DB/image-size/medium?v=v2&amp;amp;px=400" role="button" title="NetworkMonkey101_1-1731428341538.png" alt="NetworkMonkey101_1-1731428341538.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 12 Nov 2024 16:19:08 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/dns-resolution-issue-with-ise/m-p/5223320#M593145</guid>
      <dc:creator>NetworkMonkey101</dc:creator>
      <dc:date>2024-11-12T16:19:08Z</dc:date>
    </item>
    <item>
      <title>Re: DNS resolution issue with ISE</title>
      <link>https://community.cisco.com/t5/network-access-control/dns-resolution-issue-with-ise/m-p/5223347#M593146</link>
      <description>&lt;P&gt;I would try to restart ISE services and if that does not help, I would try to reload the node before getting TAC engaged.&lt;/P&gt;</description>
      <pubDate>Tue, 12 Nov 2024 17:08:50 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/dns-resolution-issue-with-ise/m-p/5223347#M593146</guid>
      <dc:creator>Aref Alsouqi</dc:creator>
      <dc:date>2024-11-12T17:08:50Z</dc:date>
    </item>
    <item>
      <title>Re: DNS resolution issue with ISE</title>
      <link>https://community.cisco.com/t5/network-access-control/dns-resolution-issue-with-ise/m-p/5296272#M596634</link>
      <description>&lt;P&gt;I was wondering if there was any resolution to this issue?&amp;nbsp; I am experiencing the same thing on an ISE server that I deployed a couple of days ago.&lt;/P&gt;</description>
      <pubDate>Tue, 03 Jun 2025 18:51:29 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/dns-resolution-issue-with-ise/m-p/5296272#M596634</guid>
      <dc:creator>kelkins</dc:creator>
      <dc:date>2025-06-03T18:51:29Z</dc:date>
    </item>
    <item>
      <title>Re: DNS resolution issue with ISE</title>
      <link>https://community.cisco.com/t5/network-access-control/dns-resolution-issue-with-ise/m-p/5296367#M596638</link>
      <description>&lt;P class="lia-align-justify"&gt;Hi&amp;nbsp;&lt;a href="https://community.cisco.com/t5/user/viewprofilepage/user-id/1708908"&gt;@kelkins&lt;/a&gt;&amp;nbsp;,&lt;/P&gt;
&lt;P class="lia-align-justify"&gt;&amp;nbsp;please take a look at:&amp;nbsp;&lt;A href="https://community.cisco.com/t5/security-knowledge-base/ise-what-we-need-to-know-about-dns-server/ta-p/5242034" target="_blank" rel="noopener"&gt;ISE - What we need to know about DNS Server&lt;/A&gt;, search for &lt;STRONG&gt;FQDN&lt;/STRONG&gt;.&lt;/P&gt;
&lt;P class="lia-align-justify"&gt;&amp;nbsp;&lt;/P&gt;
&lt;P class="lia-align-justify"&gt;Hope this helps !!!&lt;/P&gt;
&lt;P class="lia-align-justify"&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 04 Jun 2025 06:31:54 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/dns-resolution-issue-with-ise/m-p/5296367#M596638</guid>
      <dc:creator>Marcelo Morais</dc:creator>
      <dc:date>2025-06-04T06:31:54Z</dc:date>
    </item>
  </channel>
</rss>

