<?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: New DMZ ISE node not able to reach DNS on inside zone in Network Access Control</title>
    <link>https://community.cisco.com/t5/network-access-control/new-dmz-ise-node-not-able-to-reach-dns-on-inside-zone/m-p/5221425#M593060</link>
    <description>&lt;P&gt;Share packet tracer ypu run'&lt;/P&gt;
&lt;P&gt;Send it to me as PM&lt;/P&gt;
&lt;P&gt;MHM&lt;/P&gt;</description>
    <pubDate>Thu, 07 Nov 2024 11:40:44 GMT</pubDate>
    <dc:creator>MHM Cisco World</dc:creator>
    <dc:date>2024-11-07T11:40:44Z</dc:date>
    <item>
      <title>New DMZ ISE node not able to reach DNS on inside zone</title>
      <link>https://community.cisco.com/t5/network-access-control/new-dmz-ise-node-not-able-to-reach-dns-on-inside-zone/m-p/5221403#M593056</link>
      <description>&lt;P&gt;I am deploying a new ISE node which resides within a DMZ zone on FTD. During the initial bootstrapping it is failing to reach the name server .&lt;/P&gt;
&lt;P&gt;ISE node 192.168.235.12 - DMZ zone&lt;/P&gt;
&lt;P&gt;DNS 192.168.245.246&lt;/P&gt;
&lt;P&gt;I have created a policy on the FTD and ran a packet capture the traffic is allowed.. What else could be stopping this?&lt;/P&gt;</description>
      <pubDate>Thu, 07 Nov 2024 10:51:42 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/new-dmz-ise-node-not-able-to-reach-dns-on-inside-zone/m-p/5221403#M593056</guid>
      <dc:creator>blocksupport</dc:creator>
      <dc:date>2024-11-07T10:51:42Z</dc:date>
    </item>
    <item>
      <title>Re: New DMZ ISE node not able to reach DNS on inside zone</title>
      <link>https://community.cisco.com/t5/network-access-control/new-dmz-ise-node-not-able-to-reach-dns-on-inside-zone/m-p/5221419#M593058</link>
      <description>&lt;P&gt;&lt;a href="https://community.cisco.com/t5/user/viewprofilepage/user-id/320853"&gt;@blocksupport&lt;/a&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;Where the DNS server is connected? Does it have gateway or use route table?&lt;/P&gt;</description>
      <pubDate>Thu, 07 Nov 2024 11:34:38 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/new-dmz-ise-node-not-able-to-reach-dns-on-inside-zone/m-p/5221419#M593058</guid>
      <dc:creator>Flavio Miranda</dc:creator>
      <dc:date>2024-11-07T11:34:38Z</dc:date>
    </item>
    <item>
      <title>Re: New DMZ ISE node not able to reach DNS on inside zone</title>
      <link>https://community.cisco.com/t5/network-access-control/new-dmz-ise-node-not-able-to-reach-dns-on-inside-zone/m-p/5221421#M593059</link>
      <description>&lt;P&gt;What action did you apply to that rule? I would try to change it to "trust" if that is not already applied. Another thing come to mind,&amp;nbsp; in terms of routing, does the DNS server know how to reach ISE?&lt;/P&gt;</description>
      <pubDate>Thu, 07 Nov 2024 11:35:58 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/new-dmz-ise-node-not-able-to-reach-dns-on-inside-zone/m-p/5221421#M593059</guid>
      <dc:creator>Aref Alsouqi</dc:creator>
      <dc:date>2024-11-07T11:35:58Z</dc:date>
    </item>
    <item>
      <title>Re: New DMZ ISE node not able to reach DNS on inside zone</title>
      <link>https://community.cisco.com/t5/network-access-control/new-dmz-ise-node-not-able-to-reach-dns-on-inside-zone/m-p/5221425#M593060</link>
      <description>&lt;P&gt;Share packet tracer ypu run'&lt;/P&gt;
&lt;P&gt;Send it to me as PM&lt;/P&gt;
&lt;P&gt;MHM&lt;/P&gt;</description>
      <pubDate>Thu, 07 Nov 2024 11:40:44 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/new-dmz-ise-node-not-able-to-reach-dns-on-inside-zone/m-p/5221425#M593060</guid>
      <dc:creator>MHM Cisco World</dc:creator>
      <dc:date>2024-11-07T11:40:44Z</dc:date>
    </item>
  </channel>
</rss>

