<?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 Internal DNS Issue via Prisma Access in Prisma Access Discussions</title>
    <link>https://live.paloaltonetworks.com/t5/prisma-access-discussions/internal-dns-issue-via-prisma-access/m-p/1256319#M1302</link>
    <description>&lt;P&gt;Hi Team,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Recently we have done Prisma SASE deployment, below is the infra details:-&lt;/P&gt;
&lt;P&gt;1. Private Application hosted on AWS.&lt;/P&gt;
&lt;P&gt;2. Tunnel created between Prisma &amp;amp; AWS via ZTNA Connector.&lt;/P&gt;
&lt;P&gt;3. Users connect private application via Global Protect or Prisma Browser.&lt;/P&gt;
&lt;P&gt;4. Application host in AWS via Internal load balancer.&lt;/P&gt;
&lt;P&gt;5. DNS Server deployed in AWS infra.&lt;/P&gt;
&lt;P&gt;6. Internal LB cname configured in DNS Server.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Issue:&lt;/P&gt;
&lt;P&gt;Via Prisma Browser user is not able to access private application (cname).&lt;/P&gt;</description>
    <pubDate>Mon, 15 Jun 2026 05:44:46 GMT</pubDate>
    <dc:creator>Mitesh_Nandu</dc:creator>
    <dc:date>2026-06-15T05:44:46Z</dc:date>
    <item>
      <title>Internal DNS Issue via Prisma Access</title>
      <link>https://live.paloaltonetworks.com/t5/prisma-access-discussions/internal-dns-issue-via-prisma-access/m-p/1256319#M1302</link>
      <description>&lt;P&gt;Hi Team,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Recently we have done Prisma SASE deployment, below is the infra details:-&lt;/P&gt;
&lt;P&gt;1. Private Application hosted on AWS.&lt;/P&gt;
&lt;P&gt;2. Tunnel created between Prisma &amp;amp; AWS via ZTNA Connector.&lt;/P&gt;
&lt;P&gt;3. Users connect private application via Global Protect or Prisma Browser.&lt;/P&gt;
&lt;P&gt;4. Application host in AWS via Internal load balancer.&lt;/P&gt;
&lt;P&gt;5. DNS Server deployed in AWS infra.&lt;/P&gt;
&lt;P&gt;6. Internal LB cname configured in DNS Server.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Issue:&lt;/P&gt;
&lt;P&gt;Via Prisma Browser user is not able to access private application (cname).&lt;/P&gt;</description>
      <pubDate>Mon, 15 Jun 2026 05:44:46 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/prisma-access-discussions/internal-dns-issue-via-prisma-access/m-p/1256319#M1302</guid>
      <dc:creator>Mitesh_Nandu</dc:creator>
      <dc:date>2026-06-15T05:44:46Z</dc:date>
    </item>
  </channel>
</rss>

