<?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: Global Protect DNS Issue in GlobalProtect Discussions</title>
    <link>https://live.paloaltonetworks.com/t5/globalprotect-discussions/global-protect-dns-issue/m-p/591247#M5528</link>
    <description>&lt;P&gt;Seeing this on a handful of clients this week all running 6.2.2.&lt;/P&gt;</description>
    <pubDate>Fri, 05 Jul 2024 08:10:16 GMT</pubDate>
    <dc:creator>James_Martin</dc:creator>
    <dc:date>2024-07-05T08:10:16Z</dc:date>
    <item>
      <title>Global Protect DNS Issue</title>
      <link>https://live.paloaltonetworks.com/t5/globalprotect-discussions/global-protect-dns-issue/m-p/546011#M4125</link>
      <description>&lt;P&gt;Hi Team,&lt;/P&gt;
&lt;P&gt;We are facing a weird issue with GP. Random users connecting to GP is being assigned with the Loopback IP(127.0.0.1) as DNS. They have to go to settings and then remove the loopback IP from the DNS only then it starts working. This is not for all users. Random users are facing this issue.&lt;/P&gt;
&lt;P&gt;Anyone faced this kind of issue? or any input on this is very helpful.&lt;/P&gt;
&lt;P&gt;Regards,&lt;/P&gt;
&lt;P&gt;Sanjay S&lt;/P&gt;</description>
      <pubDate>Wed, 14 Jun 2023 12:12:33 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/globalprotect-discussions/global-protect-dns-issue/m-p/546011#M4125</guid>
      <dc:creator>Sanjay_Ramaiah</dc:creator>
      <dc:date>2023-06-14T12:12:33Z</dc:date>
    </item>
    <item>
      <title>Re: Global Protect DNS Issue</title>
      <link>https://live.paloaltonetworks.com/t5/globalprotect-discussions/global-protect-dns-issue/m-p/552093#M4244</link>
      <description>&lt;P&gt;I am experiencing the exact same thing. I have switched to a few different GP Client versions and no change. A solution here would be great.&lt;/P&gt;</description>
      <pubDate>Tue, 01 Aug 2023 15:58:17 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/globalprotect-discussions/global-protect-dns-issue/m-p/552093#M4244</guid>
      <dc:creator>CDuPlessis1</dc:creator>
      <dc:date>2023-08-01T15:58:17Z</dc:date>
    </item>
    <item>
      <title>Re: Global Protect DNS Issue</title>
      <link>https://live.paloaltonetworks.com/t5/globalprotect-discussions/global-protect-dns-issue/m-p/591247#M5528</link>
      <description>&lt;P&gt;Seeing this on a handful of clients this week all running 6.2.2.&lt;/P&gt;</description>
      <pubDate>Fri, 05 Jul 2024 08:10:16 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/globalprotect-discussions/global-protect-dns-issue/m-p/591247#M5528</guid>
      <dc:creator>James_Martin</dc:creator>
      <dc:date>2024-07-05T08:10:16Z</dc:date>
    </item>
    <item>
      <title>Re: Global Protect DNS Issue</title>
      <link>https://live.paloaltonetworks.com/t5/globalprotect-discussions/global-protect-dns-issue/m-p/591340#M5538</link>
      <description>&lt;P&gt;Hi All,&lt;/P&gt;
&lt;P&gt;For me upgrading the GP clients to the Palo suggested version helped. Since then no issues reported by customer.&lt;/P&gt;</description>
      <pubDate>Mon, 08 Jul 2024 08:02:15 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/globalprotect-discussions/global-protect-dns-issue/m-p/591340#M5538</guid>
      <dc:creator>Sanjay_Ramaiah</dc:creator>
      <dc:date>2024-07-08T08:02:15Z</dc:date>
    </item>
  </channel>
</rss>

