<?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 GlobalProtect Clients Home IP's showing up in DNS in GlobalProtect Discussions</title>
    <link>https://live.paloaltonetworks.com/t5/globalprotect-discussions/globalprotect-clients-home-ip-s-showing-up-in-dns/m-p/322559#M18</link>
    <description>&lt;P&gt;Like many organizations, we have had to enable VPN access for more individuals during the COVID-19 crisis. We recently noticed that about half of the 42 machines display their home's local LAN IP address in our DNS server. This is in addition to the IP address that GlobalProtect issues. One of my sysadmins pointed out a way to fix this is to disable the&amp;nbsp;&lt;STRONG&gt;Register this connection's addresses in DNS&amp;nbsp;&lt;/STRONG&gt;feature on the Ethernet or wireless NIC adapter in Windows 10 (not the PANGP adapter). This would stop the adapter from sending the 192.168.x.x IP to our DNS server and adding it to the A record.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="nic setting.png" style="width: 414px;"&gt;&lt;img src="https://live.paloaltonetworks.com/t5/image/serverpage/image-id/25148i09B09F724B96A24A/image-size/large/is-moderation-mode/true?v=v2&amp;amp;px=999" role="button" title="nic setting.png" alt="nic setting.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Is there another way to get around this?&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Mon, 13 Apr 2020 23:22:38 GMT</pubDate>
    <dc:creator>Fr4nk4</dc:creator>
    <dc:date>2020-04-13T23:22:38Z</dc:date>
    <item>
      <title>GlobalProtect Clients Home IP's showing up in DNS</title>
      <link>https://live.paloaltonetworks.com/t5/globalprotect-discussions/globalprotect-clients-home-ip-s-showing-up-in-dns/m-p/322559#M18</link>
      <description>&lt;P&gt;Like many organizations, we have had to enable VPN access for more individuals during the COVID-19 crisis. We recently noticed that about half of the 42 machines display their home's local LAN IP address in our DNS server. This is in addition to the IP address that GlobalProtect issues. One of my sysadmins pointed out a way to fix this is to disable the&amp;nbsp;&lt;STRONG&gt;Register this connection's addresses in DNS&amp;nbsp;&lt;/STRONG&gt;feature on the Ethernet or wireless NIC adapter in Windows 10 (not the PANGP adapter). This would stop the adapter from sending the 192.168.x.x IP to our DNS server and adding it to the A record.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="nic setting.png" style="width: 414px;"&gt;&lt;img src="https://live.paloaltonetworks.com/t5/image/serverpage/image-id/25148i09B09F724B96A24A/image-size/large/is-moderation-mode/true?v=v2&amp;amp;px=999" role="button" title="nic setting.png" alt="nic setting.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Is there another way to get around this?&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 13 Apr 2020 23:22:38 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/globalprotect-discussions/globalprotect-clients-home-ip-s-showing-up-in-dns/m-p/322559#M18</guid>
      <dc:creator>Fr4nk4</dc:creator>
      <dc:date>2020-04-13T23:22:38Z</dc:date>
    </item>
    <item>
      <title>Re: GlobalProtect Clients Home IP's showing up in DNS</title>
      <link>https://live.paloaltonetworks.com/t5/globalprotect-discussions/globalprotect-clients-home-ip-s-showing-up-in-dns/m-p/322774#M20</link>
      <description>&lt;P&gt;Hi Fr4nk4,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Please go through this link to remove the local IP from dns record:&amp;nbsp;&lt;A href="https://support.microsoft.com/en-us/help/2933537/clearing-the-register-this-connection-s-addresses-in-dns-option-does-n" target="_blank"&gt;https://support.microsoft.com/en-us/help/2933537/clearing-the-register-this-connection-s-addresses-in-dns-option-does-n&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I am not sure of another way to do this. What made you select that option in the first place?&lt;/P&gt;</description>
      <pubDate>Wed, 15 Apr 2020 00:16:06 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/globalprotect-discussions/globalprotect-clients-home-ip-s-showing-up-in-dns/m-p/322774#M20</guid>
      <dc:creator>vathreya</dc:creator>
      <dc:date>2020-04-15T00:16:06Z</dc:date>
    </item>
    <item>
      <title>Re: GlobalProtect Clients Home IP's showing up in DNS</title>
      <link>https://live.paloaltonetworks.com/t5/globalprotect-discussions/globalprotect-clients-home-ip-s-showing-up-in-dns/m-p/324097#M71</link>
      <description>&lt;P&gt;I've posted this on a couple forums now, and it seems like this is an issue regardless of which VPN solution you use. That option to register this connection's address in DNS is a default option in our Windows 10 image. We got around it by looking up the GP IP for the user, edit our hosts file entry with the GP IP and the FQDN, and then issuing the following commands to remotely connect to the computer and uncheck that DNS option. We eventually put this into a script, and now a GPO.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;#Connect remotely to multiple computers using admin Account&lt;BR /&gt;Enter-PSSession –ComputerName &lt;EM&gt;mycomputername&lt;/EM&gt; –Credential &lt;EM&gt;domain\username&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;#Check to see if DNS registry option is checked&lt;/P&gt;&lt;P&gt;Get-NetAdapter Ethernet | Get-DNSClient&lt;BR /&gt;Get-NetAdapter Wi-Fi | Get-DNSClient&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;&lt;P&gt;#Sets the DNS Registry option on Ethernet interface to False (turns off)&lt;/P&gt;&lt;P&gt;Get-NetAdapter Ethernet | Set-DNSClient –RegisterThisConnectionsAddress $False&lt;BR /&gt;Get-NetAdapter Wi-Fi| Set-DNSClient –RegisterThisConnectionsAddress $False&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;#Force ipconfig /registerdns&lt;/P&gt;&lt;P&gt;Register-DnsClient&lt;/P&gt;</description>
      <pubDate>Tue, 21 Apr 2020 17:00:28 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/globalprotect-discussions/globalprotect-clients-home-ip-s-showing-up-in-dns/m-p/324097#M71</guid>
      <dc:creator>Fr4nk4</dc:creator>
      <dc:date>2020-04-21T17:00:28Z</dc:date>
    </item>
    <item>
      <title>Re: GlobalProtect Clients Home IP's showing up in DNS</title>
      <link>https://live.paloaltonetworks.com/t5/globalprotect-discussions/globalprotect-clients-home-ip-s-showing-up-in-dns/m-p/566507#M4648</link>
      <description>&lt;P&gt;HiGuys,&lt;/P&gt;
&lt;P&gt;I have a client and they want to keep the "Register this connection's addresses in DNS" option enabled as they want to use WIFI provided addresses when workers are in office and use GP provided address when working from home. Is there any other way to fix duplicate IP problem on DNS server.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 21 Nov 2023 14:36:03 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/globalprotect-discussions/globalprotect-clients-home-ip-s-showing-up-in-dns/m-p/566507#M4648</guid>
      <dc:creator>MansoorAli</dc:creator>
      <dc:date>2023-11-21T14:36:03Z</dc:date>
    </item>
  </channel>
</rss>

