<?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: DNS resolution is not happening after connected the Global protect in General Topics</title>
    <link>https://live.paloaltonetworks.com/t5/general-topics/dns-resolution-is-not-happening-after-connected-the-global/m-p/295764#M77886</link>
    <description>&lt;P&gt;&lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/106720"&gt;@MohammedAsik&lt;/a&gt;&amp;nbsp; Do you have DNS Suffix configured in Agent configuration ??&lt;/P&gt;</description>
    <pubDate>Fri, 01 Nov 2019 20:56:49 GMT</pubDate>
    <dc:creator>pkathiria</dc:creator>
    <dc:date>2019-11-01T20:56:49Z</dc:date>
    <item>
      <title>DNS resolution is not happening after connected the Global protect</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/dns-resolution-is-not-happening-after-connected-the-global/m-p/295690#M77877</link>
      <description>&lt;P&gt;Hi Team&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;1. After connected the global protect DNS resolution is not happening. but i can able to do ping 8.8.8.8.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;2. In nslookup google.com also resolved. But if I ping the same google.com dns is not resolving.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;3. If I browse any website, that is not working due to dns resolution issue.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;My dns IP is 8.8.8.8. Is anyone experienced like this type of issue. Please suggest some resolution for this&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Best regards&lt;/P&gt;&lt;P&gt;Mohammed Asik&lt;/P&gt;</description>
      <pubDate>Fri, 01 Nov 2019 15:31:08 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/dns-resolution-is-not-happening-after-connected-the-global/m-p/295690#M77877</guid>
      <dc:creator>MohammedAsik</dc:creator>
      <dc:date>2019-11-01T15:31:08Z</dc:date>
    </item>
    <item>
      <title>Re: DNS resolution is not happening after connected the Global protect</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/dns-resolution-is-not-happening-after-connected-the-global/m-p/295700#M77878</link>
      <description>&lt;P&gt;What do you see in the traffic logs?&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 01 Nov 2019 16:08:27 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/dns-resolution-is-not-happening-after-connected-the-global/m-p/295700#M77878</guid>
      <dc:creator>myky</dc:creator>
      <dc:date>2019-11-01T16:08:27Z</dc:date>
    </item>
    <item>
      <title>Re: DNS resolution is not happening after connected the Global protect</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/dns-resolution-is-not-happening-after-connected-the-global/m-p/295709#M77880</link>
      <description>&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;In traffic logs, I could see the session reason end was " aged out". But everything seems to be expected.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;For internet traffic NAT applied and could see destination address ip has been resolved. but in web browser its not resolved ( tried the same thing with three different machines.&lt;/P&gt;&lt;P&gt;ingress interface --&amp;gt; tunnel.2 and egress interface --&amp;gt; eth 1/2 as per the configuration&lt;/P&gt;</description>
      <pubDate>Fri, 01 Nov 2019 16:26:41 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/dns-resolution-is-not-happening-after-connected-the-global/m-p/295709#M77880</guid>
      <dc:creator>MohammedAsik</dc:creator>
      <dc:date>2019-11-01T16:26:41Z</dc:date>
    </item>
    <item>
      <title>Re: DNS resolution is not happening after connected the Global protect</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/dns-resolution-is-not-happening-after-connected-the-global/m-p/295710#M77881</link>
      <description>&lt;P&gt;for DNS and web-browsing traffic bytes sent/received increment equally (or more less)?&lt;/P&gt;</description>
      <pubDate>Fri, 01 Nov 2019 16:30:19 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/dns-resolution-is-not-happening-after-connected-the-global/m-p/295710#M77881</guid>
      <dc:creator>myky</dc:creator>
      <dc:date>2019-11-01T16:30:19Z</dc:date>
    </item>
    <item>
      <title>Re: DNS resolution is not happening after connected the Global protect</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/dns-resolution-is-not-happening-after-connected-the-global/m-p/295764#M77886</link>
      <description>&lt;P&gt;&lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/106720"&gt;@MohammedAsik&lt;/a&gt;&amp;nbsp; Do you have DNS Suffix configured in Agent configuration ??&lt;/P&gt;</description>
      <pubDate>Fri, 01 Nov 2019 20:56:49 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/dns-resolution-is-not-happening-after-connected-the-global/m-p/295764#M77886</guid>
      <dc:creator>pkathiria</dc:creator>
      <dc:date>2019-11-01T20:56:49Z</dc:date>
    </item>
    <item>
      <title>Re: DNS resolution is not happening after connected the Global protect</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/dns-resolution-is-not-happening-after-connected-the-global/m-p/326689#M83217</link>
      <description>&lt;P&gt;I have GP agents experiencing&amp;nbsp;the same issue.&amp;nbsp; Did you find a resolution?&lt;/P&gt;</description>
      <pubDate>Thu, 07 May 2020 16:05:04 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/dns-resolution-is-not-happening-after-connected-the-global/m-p/326689#M83217</guid>
      <dc:creator>ice-quake</dc:creator>
      <dc:date>2020-05-07T16:05:04Z</dc:date>
    </item>
  </channel>
</rss>

