<?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: ISE DNS health check showing warning in Network Access Control</title>
    <link>https://community.cisco.com/t5/network-access-control/ise-dns-health-check-showing-warning/m-p/5072769#M588836</link>
    <description>&lt;P&gt;I had a similar issue with a customer of mine a few months back, and the issue was caused by a buggy behaviour of ISE. If I remember correctly we could fix the issue by swapping the DNS servers order and then putting them back to how they were before.&lt;/P&gt;</description>
    <pubDate>Thu, 18 Apr 2024 09:05:11 GMT</pubDate>
    <dc:creator>Aref Alsouqi</dc:creator>
    <dc:date>2024-04-18T09:05:11Z</dc:date>
    <item>
      <title>ISE DNS health check showing warning</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-dns-health-check-showing-warning/m-p/5072545#M588833</link>
      <description>&lt;P&gt;Hi all,&lt;/P&gt;&lt;P&gt;I have a four new standalone nodes which will be going into a cluster, I am seeing two nodes have a DNS warning. All nodes are located in the same ca&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="NetworkMonkey101_0-1713418948817.png" style="width: 400px;"&gt;&lt;img src="https://community.cisco.com/t5/image/serverpage/image-id/216059iBAD91A4CC69C226E/image-size/medium?v=v2&amp;amp;px=400" role="button" title="NetworkMonkey101_0-1713418948817.png" alt="NetworkMonkey101_0-1713418948817.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;I can ping both DNS servers .21 and .22 and nslookup up works to resolve its own IP&lt;/P&gt;&lt;P&gt;Why are two showing this?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 18 Apr 2024 05:47:32 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-dns-health-check-showing-warning/m-p/5072545#M588833</guid>
      <dc:creator>NetworkMonkey101</dc:creator>
      <dc:date>2024-04-18T05:47:32Z</dc:date>
    </item>
    <item>
      <title>Re: ISE DNS health check showing warning</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-dns-health-check-showing-warning/m-p/5072626#M588835</link>
      <description>&lt;P&gt;Do you have DNS Entry for that pan node which is failing ?&lt;/P&gt;
&lt;P&gt;if your PC using same DNS, are you able to resolve that ?&lt;/P&gt;
&lt;P&gt;All the ISE node giving same error ?&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 18 Apr 2024 07:19:54 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-dns-health-check-showing-warning/m-p/5072626#M588835</guid>
      <dc:creator>balaji.bandi</dc:creator>
      <dc:date>2024-04-18T07:19:54Z</dc:date>
    </item>
    <item>
      <title>Re: ISE DNS health check showing warning</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-dns-health-check-showing-warning/m-p/5072769#M588836</link>
      <description>&lt;P&gt;I had a similar issue with a customer of mine a few months back, and the issue was caused by a buggy behaviour of ISE. If I remember correctly we could fix the issue by swapping the DNS servers order and then putting them back to how they were before.&lt;/P&gt;</description>
      <pubDate>Thu, 18 Apr 2024 09:05:11 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-dns-health-check-showing-warning/m-p/5072769#M588836</guid>
      <dc:creator>Aref Alsouqi</dc:creator>
      <dc:date>2024-04-18T09:05:11Z</dc:date>
    </item>
  </channel>
</rss>

