<?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: Reverse dns in ISE distributed deployment in Network Access Control</title>
    <link>https://community.cisco.com/t5/network-access-control/reverse-dns-in-ise-distributed-deployment/m-p/3566420#M509651</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;﻿Reverse DNS is required for ISE deployments, otherwise run into numerous issues&lt;/P&gt;&lt;P&gt;https://bst.cloudapps.cisco.com/bugsearch/bug/CSCuj29194/?rfs=iqvred&lt;/P&gt;&lt;P&gt;https://communities.cisco.com/message/280378&lt;/P&gt;&lt;P&gt;https://www.cisco.com/c/en/us/td/docs/security/ise/2-3/admin_guide/b_ise_admin_guide_23/b_ise_admin_guide_23_chapter_011.html#ID209&lt;/P&gt;&lt;P&gt;·         Configure the forward and reverse DNS lookup for all Cisco ISE nodes in your distributed deployment in the DNS server. Otherwise, you may run into deployment related issues when registering and restarting Cisco ISE nodes. Performance might be degraded if reverse DNS lookup is not configured for all the nodes.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 24 May 2018 14:42:13 GMT</pubDate>
    <dc:creator>Jason Kunst</dc:creator>
    <dc:date>2018-05-24T14:42:13Z</dc:date>
    <item>
      <title>Reverse dns in ISE distributed deployment</title>
      <link>https://community.cisco.com/t5/network-access-control/reverse-dns-in-ise-distributed-deployment/m-p/3566419#M509649</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I am working on ISE distributed deployment with ISE 2.3 with patch 3. &lt;/P&gt;&lt;P&gt;From cisco official document, we need both forward and reverse dns record resolvable for all ise nodes. Customer uses cloud-based dns solution and have some issues to have reverse dns working. So customer likes to know&lt;/P&gt;&lt;P&gt;1. Which feature/function replies on reverse dns. &lt;/P&gt;&lt;P&gt;2. if we don't have reverse dns, what is the impact during or post ise distributed deployment.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 24 May 2018 03:40:45 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/reverse-dns-in-ise-distributed-deployment/m-p/3566419#M509649</guid>
      <dc:creator>xili5</dc:creator>
      <dc:date>2018-05-24T03:40:45Z</dc:date>
    </item>
    <item>
      <title>Re: Reverse dns in ISE distributed deployment</title>
      <link>https://community.cisco.com/t5/network-access-control/reverse-dns-in-ise-distributed-deployment/m-p/3566420#M509651</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;﻿Reverse DNS is required for ISE deployments, otherwise run into numerous issues&lt;/P&gt;&lt;P&gt;https://bst.cloudapps.cisco.com/bugsearch/bug/CSCuj29194/?rfs=iqvred&lt;/P&gt;&lt;P&gt;https://communities.cisco.com/message/280378&lt;/P&gt;&lt;P&gt;https://www.cisco.com/c/en/us/td/docs/security/ise/2-3/admin_guide/b_ise_admin_guide_23/b_ise_admin_guide_23_chapter_011.html#ID209&lt;/P&gt;&lt;P&gt;·         Configure the forward and reverse DNS lookup for all Cisco ISE nodes in your distributed deployment in the DNS server. Otherwise, you may run into deployment related issues when registering and restarting Cisco ISE nodes. Performance might be degraded if reverse DNS lookup is not configured for all the nodes.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 24 May 2018 14:42:13 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/reverse-dns-in-ise-distributed-deployment/m-p/3566420#M509651</guid>
      <dc:creator>Jason Kunst</dc:creator>
      <dc:date>2018-05-24T14:42:13Z</dc:date>
    </item>
  </channel>
</rss>

