<?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 DNS Query Blocking for Remote VPN Users in GlobalProtect Discussions</title>
    <link>https://live.paloaltonetworks.com/t5/globalprotect-discussions/dns-query-blocking-for-remote-vpn-users/m-p/591302#M5535</link>
    <description>&lt;P&gt;We have an environment that has a requirement where GP DNS Queries need to be blocked from Remote VPN users if those queries are destined to specific domains A and B (proxy servers). This requirement aims to achieve split-tunneling where a remote VPN user would reach the cloud server of these&amp;nbsp;domains but using the host physical interface when reaching out to those specific domains, instead of being backhauled through the GP VPN tunnel. We have been able to achieve something similar in Cisco through Cisco DNS policies and were able to define the action NXDOMAIN for query responses received through Remote VPN tunnel which result in user reaching out to the domains through physical interface but we are trying to achieve the same using GP Agent.&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;Important values about the GP configuration&amp;nbsp;&lt;BR /&gt;On-Demand&amp;nbsp;&lt;BR /&gt;Split-Tunnel Option: Network Traffic only&amp;nbsp;&lt;BR /&gt;Resolve All FQDN using DNS Servers assigned: Yes&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;</description>
    <pubDate>Sat, 06 Jul 2024 21:46:53 GMT</pubDate>
    <dc:creator>User868</dc:creator>
    <dc:date>2024-07-06T21:46:53Z</dc:date>
    <item>
      <title>DNS Query Blocking for Remote VPN Users</title>
      <link>https://live.paloaltonetworks.com/t5/globalprotect-discussions/dns-query-blocking-for-remote-vpn-users/m-p/591302#M5535</link>
      <description>&lt;P&gt;We have an environment that has a requirement where GP DNS Queries need to be blocked from Remote VPN users if those queries are destined to specific domains A and B (proxy servers). This requirement aims to achieve split-tunneling where a remote VPN user would reach the cloud server of these&amp;nbsp;domains but using the host physical interface when reaching out to those specific domains, instead of being backhauled through the GP VPN tunnel. We have been able to achieve something similar in Cisco through Cisco DNS policies and were able to define the action NXDOMAIN for query responses received through Remote VPN tunnel which result in user reaching out to the domains through physical interface but we are trying to achieve the same using GP Agent.&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;Important values about the GP configuration&amp;nbsp;&lt;BR /&gt;On-Demand&amp;nbsp;&lt;BR /&gt;Split-Tunnel Option: Network Traffic only&amp;nbsp;&lt;BR /&gt;Resolve All FQDN using DNS Servers assigned: Yes&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;</description>
      <pubDate>Sat, 06 Jul 2024 21:46:53 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/globalprotect-discussions/dns-query-blocking-for-remote-vpn-users/m-p/591302#M5535</guid>
      <dc:creator>User868</dc:creator>
      <dc:date>2024-07-06T21:46:53Z</dc:date>
    </item>
  </channel>
</rss>

