<?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 Strange DNS behavior - Mobile Users—GlobalProtect - Panorama Managed Prisma Access in GlobalProtect Discussions</title>
    <link>https://live.paloaltonetworks.com/t5/globalprotect-discussions/strange-dns-behavior-mobile-users-globalprotect-panorama-managed/m-p/510272#M3045</link>
    <description>&lt;P&gt;Hi everyone,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I had a bit of a strange behavior regarding DNS for mobile users, and wanted to verify if this was working as intended.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;EM&gt;IP addresses are made up&lt;/EM&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Info on the infrastructure:&lt;/P&gt;
&lt;P&gt;-&amp;nbsp;Panorama Managed Prisma Access.&lt;/P&gt;
&lt;P&gt;-&amp;nbsp;Mobile Users - GlobalProtect.&lt;/P&gt;
&lt;P&gt;- Using both On-Premises and Prisma Access gateways (Manual).&lt;/P&gt;
&lt;P&gt;- DNS for internal domains configured in "Network Services" (&lt;SPAN&gt;10.1.1.1 &amp;amp; 10.2.2.2)&lt;/SPAN&gt; through the Prisma Access cloud services plugin, with public domains using the cloud defaults.&lt;/P&gt;
&lt;P&gt;- On-Premises gateways assigning&amp;nbsp;&lt;SPAN&gt;10.1.1.1 &amp;amp; 10.2.2.2 as DNS servers.&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;The behavior:&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;- GlobalProtect clients connected directly through on-prem external gateways, was able to do internal DNS lookups, and ping internal FQDNs.&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;-&amp;nbsp;&lt;SPAN&gt;GlobalProtect clients connected through Prisma Access country specific location gateways, received DNS configuration of .1 in their assigned scope.&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;- GlobalProtect clients connected through Prisma Access country specific location gateways, was able to do DNS lookups (not directly to DNS servers 10.1.1.1 &amp;amp; 10.2.2.2), but not able to ping internal FQDNs. Though able to ping the IP address received from the DNS lookups.&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;Solution:&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;-&amp;nbsp;After configuring DNS servers 10.1.1.1 &amp;amp; 10.2.2.2 with suffix under (Template Mobile_User_Template) Network -&amp;gt; Gateways -&amp;gt; GlobalProtect_External_Gateway -&amp;gt; Agent -&amp;gt; Client Settings -&amp;gt; DEFAULT -&amp;gt; Network Services, the clients connecting through Prisma Access country specific location gateways, received the correct DNS configuration and was able to do internal DNS lookups, and ping internal FQDNs.&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;Following Palo Alto's own documentation (&lt;A href="https://docs.paloaltonetworks.com/prisma/prisma-access/prisma-access-panorama-admin/prisma-access-for-users/globalprotect-prisma-access/configure-prisma-access-for-users#id174HA00B0Y4" target="_blank"&gt;https://docs.paloaltonetworks.com/prisma/prisma-access/prisma-access-panorama-admin/prisma-access-for-users/globalprotect-prisma-access/configure-prisma-access-for-users#id174HA00B0Y4&lt;/A&gt;), there in no mentioning of this, and only configuring through the Prisma Access plugin should suffice.&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;Hope I can get some clarification on this.&lt;/SPAN&gt;&lt;/P&gt;</description>
    <pubDate>Fri, 29 Jul 2022 09:00:49 GMT</pubDate>
    <dc:creator>KasperT</dc:creator>
    <dc:date>2022-07-29T09:00:49Z</dc:date>
    <item>
      <title>Strange DNS behavior - Mobile Users—GlobalProtect - Panorama Managed Prisma Access</title>
      <link>https://live.paloaltonetworks.com/t5/globalprotect-discussions/strange-dns-behavior-mobile-users-globalprotect-panorama-managed/m-p/510272#M3045</link>
      <description>&lt;P&gt;Hi everyone,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I had a bit of a strange behavior regarding DNS for mobile users, and wanted to verify if this was working as intended.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;EM&gt;IP addresses are made up&lt;/EM&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Info on the infrastructure:&lt;/P&gt;
&lt;P&gt;-&amp;nbsp;Panorama Managed Prisma Access.&lt;/P&gt;
&lt;P&gt;-&amp;nbsp;Mobile Users - GlobalProtect.&lt;/P&gt;
&lt;P&gt;- Using both On-Premises and Prisma Access gateways (Manual).&lt;/P&gt;
&lt;P&gt;- DNS for internal domains configured in "Network Services" (&lt;SPAN&gt;10.1.1.1 &amp;amp; 10.2.2.2)&lt;/SPAN&gt; through the Prisma Access cloud services plugin, with public domains using the cloud defaults.&lt;/P&gt;
&lt;P&gt;- On-Premises gateways assigning&amp;nbsp;&lt;SPAN&gt;10.1.1.1 &amp;amp; 10.2.2.2 as DNS servers.&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;The behavior:&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;- GlobalProtect clients connected directly through on-prem external gateways, was able to do internal DNS lookups, and ping internal FQDNs.&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;-&amp;nbsp;&lt;SPAN&gt;GlobalProtect clients connected through Prisma Access country specific location gateways, received DNS configuration of .1 in their assigned scope.&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;- GlobalProtect clients connected through Prisma Access country specific location gateways, was able to do DNS lookups (not directly to DNS servers 10.1.1.1 &amp;amp; 10.2.2.2), but not able to ping internal FQDNs. Though able to ping the IP address received from the DNS lookups.&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;Solution:&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;-&amp;nbsp;After configuring DNS servers 10.1.1.1 &amp;amp; 10.2.2.2 with suffix under (Template Mobile_User_Template) Network -&amp;gt; Gateways -&amp;gt; GlobalProtect_External_Gateway -&amp;gt; Agent -&amp;gt; Client Settings -&amp;gt; DEFAULT -&amp;gt; Network Services, the clients connecting through Prisma Access country specific location gateways, received the correct DNS configuration and was able to do internal DNS lookups, and ping internal FQDNs.&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;Following Palo Alto's own documentation (&lt;A href="https://docs.paloaltonetworks.com/prisma/prisma-access/prisma-access-panorama-admin/prisma-access-for-users/globalprotect-prisma-access/configure-prisma-access-for-users#id174HA00B0Y4" target="_blank"&gt;https://docs.paloaltonetworks.com/prisma/prisma-access/prisma-access-panorama-admin/prisma-access-for-users/globalprotect-prisma-access/configure-prisma-access-for-users#id174HA00B0Y4&lt;/A&gt;), there in no mentioning of this, and only configuring through the Prisma Access plugin should suffice.&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;Hope I can get some clarification on this.&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Fri, 29 Jul 2022 09:00:49 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/globalprotect-discussions/strange-dns-behavior-mobile-users-globalprotect-panorama-managed/m-p/510272#M3045</guid>
      <dc:creator>KasperT</dc:creator>
      <dc:date>2022-07-29T09:00:49Z</dc:date>
    </item>
  </channel>
</rss>

