<?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 and global protect in GlobalProtect Discussions</title>
    <link>https://live.paloaltonetworks.com/t5/globalprotect-discussions/dns-and-global-protect/m-p/486455#M2745</link>
    <description>&lt;P&gt;I have a situation where global protect clients are dished out a DHCP address from the firewall but need an on-prem PTR created when they connect. does anyone have a good way to do this ?&amp;nbsp;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Wed, 11 May 2022 20:10:07 GMT</pubDate>
    <dc:creator>C_Neal</dc:creator>
    <dc:date>2022-05-11T20:10:07Z</dc:date>
    <item>
      <title>DNS and global protect</title>
      <link>https://live.paloaltonetworks.com/t5/globalprotect-discussions/dns-and-global-protect/m-p/486455#M2745</link>
      <description>&lt;P&gt;I have a situation where global protect clients are dished out a DHCP address from the firewall but need an on-prem PTR created when they connect. does anyone have a good way to do this ?&amp;nbsp;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 11 May 2022 20:10:07 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/globalprotect-discussions/dns-and-global-protect/m-p/486455#M2745</guid>
      <dc:creator>C_Neal</dc:creator>
      <dc:date>2022-05-11T20:10:07Z</dc:date>
    </item>
    <item>
      <title>Re: DNS and global protect</title>
      <link>https://live.paloaltonetworks.com/t5/globalprotect-discussions/dns-and-global-protect/m-p/486571#M2748</link>
      <description>&lt;P&gt;&lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/188676"&gt;@C_Neal&lt;/a&gt;,&lt;/P&gt;
&lt;P&gt;This can definitely be done by the&amp;nbsp;&lt;EM&gt;client&amp;nbsp;&lt;/EM&gt;and not the firewall. As long as you have a domain environment, the clients update their own PTR records and the DHCP server itself doesn't need to be involved. Have you verified that your Windows guys have actually added the VPN DHCP pool(s) in the forward lookup zone and reverse lookup zones?&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 12 May 2022 01:50:14 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/globalprotect-discussions/dns-and-global-protect/m-p/486571#M2748</guid>
      <dc:creator>BPry</dc:creator>
      <dc:date>2022-05-12T01:50:14Z</dc:date>
    </item>
    <item>
      <title>Re: DNS and global protect</title>
      <link>https://live.paloaltonetworks.com/t5/globalprotect-discussions/dns-and-global-protect/m-p/487457#M2769</link>
      <description>&lt;P&gt;the pools were there.. we adjusted a GPO to force the ptr creation and now it's good. Thank you!!!&lt;/P&gt;</description>
      <pubDate>Mon, 16 May 2022 13:51:47 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/globalprotect-discussions/dns-and-global-protect/m-p/487457#M2769</guid>
      <dc:creator>C_Neal</dc:creator>
      <dc:date>2022-05-16T13:51:47Z</dc:date>
    </item>
  </channel>
</rss>

