<?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 Setup Cloud Only workstations in Network Access Control</title>
    <link>https://community.cisco.com/t5/network-access-control/ise-dns-setup-cloud-only-workstations/m-p/5075183#M588895</link>
    <description>Yes or use whatever DNS service the cloud service provider offers&lt;BR /&gt;</description>
    <pubDate>Mon, 22 Apr 2024 12:06:29 GMT</pubDate>
    <dc:creator>ahollifield</dc:creator>
    <dc:date>2024-04-22T12:06:29Z</dc:date>
    <item>
      <title>ISE DNS Setup Cloud Only workstations</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-dns-setup-cloud-only-workstations/m-p/5066375#M588686</link>
      <description>&lt;P&gt;I am setting up ISE in Azure for a cloud only environment. There is no on-premises infrastructure, therefore no internal DNS for lookups. I've gone through the deploy docs and can't seem to find anything regarding the DNS setup in Azure. All workstations are Azure AD joined and they use ISP for DNS. Can someone give me some guidance on setting this up please?&lt;/P&gt;
&lt;P&gt;Thanks&lt;/P&gt;
&lt;P&gt;Phil&lt;/P&gt;</description>
      <pubDate>Thu, 11 Apr 2024 13:27:04 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-dns-setup-cloud-only-workstations/m-p/5066375#M588686</guid>
      <dc:creator>plevine23</dc:creator>
      <dc:date>2024-04-11T13:27:04Z</dc:date>
    </item>
    <item>
      <title>Re: ISE DNS Setup Cloud Only workstations</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-dns-setup-cloud-only-workstations/m-p/5066402#M588687</link>
      <description>&lt;P&gt;ISE requires forward and reverse DNS records for all ISE nodes.&amp;nbsp; What DNS provider is used for all of the other workloads in Azure?&amp;nbsp; The DNS server doesn't have to be on-prem.&lt;/P&gt;</description>
      <pubDate>Thu, 11 Apr 2024 13:49:56 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-dns-setup-cloud-only-workstations/m-p/5066402#M588687</guid>
      <dc:creator>ahollifield</dc:creator>
      <dc:date>2024-04-11T13:49:56Z</dc:date>
    </item>
    <item>
      <title>Re: ISE DNS Setup Cloud Only workstations</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-dns-setup-cloud-only-workstations/m-p/5066572#M588693</link>
      <description>&lt;P&gt;There are no other workloads in Azure. Everything is either office.com or a 3rd party saml integrated app.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 11 Apr 2024 16:21:10 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-dns-setup-cloud-only-workstations/m-p/5066572#M588693</guid>
      <dc:creator>plevine23</dc:creator>
      <dc:date>2024-04-11T16:21:10Z</dc:date>
    </item>
    <item>
      <title>Re: ISE DNS Setup Cloud Only workstations</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-dns-setup-cloud-only-workstations/m-p/5066607#M588695</link>
      <description>&lt;P&gt;So there is no internal DNS server?&amp;nbsp; Everything is SaaS?&amp;nbsp; You need a DNS server for ISE to work properly with A and PTR records for all ISE nodes.&lt;/P&gt;</description>
      <pubDate>Thu, 11 Apr 2024 17:38:11 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-dns-setup-cloud-only-workstations/m-p/5066607#M588695</guid>
      <dc:creator>ahollifield</dc:creator>
      <dc:date>2024-04-11T17:38:11Z</dc:date>
    </item>
    <item>
      <title>Re: ISE DNS Setup Cloud Only workstations</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-dns-setup-cloud-only-workstations/m-p/5075171#M588894</link>
      <description>&lt;P&gt;Sorry for the delayed response, but there in no Internal DNS because there's no internal infrastructure. if what you're saying is true, then I will build a DNS server and let the ISE nodes register their A and PTR records.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 22 Apr 2024 11:53:10 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-dns-setup-cloud-only-workstations/m-p/5075171#M588894</guid>
      <dc:creator>plevine23</dc:creator>
      <dc:date>2024-04-22T11:53:10Z</dc:date>
    </item>
    <item>
      <title>Re: ISE DNS Setup Cloud Only workstations</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-dns-setup-cloud-only-workstations/m-p/5075183#M588895</link>
      <description>Yes or use whatever DNS service the cloud service provider offers&lt;BR /&gt;</description>
      <pubDate>Mon, 22 Apr 2024 12:06:29 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-dns-setup-cloud-only-workstations/m-p/5075183#M588895</guid>
      <dc:creator>ahollifield</dc:creator>
      <dc:date>2024-04-22T12:06:29Z</dc:date>
    </item>
  </channel>
</rss>

