GP client update fails to download, DNS record needed

[MikeSangray2019]

We're updating from 5.2.12 to 6.2.1. The transparent update only works when testing with a DNS entry in a local hosts file. I don't think we've had a DNS entry in the past for the portal, but it seems like it's needed now.

The below article talks about this, but I want to understand which address needs to be resolved. Is it the loopback interface assigned to the portal?

GlobalProtect client upgrades failing to complete. - Knowledge Base - Palo Alto Networks

[aleksandar.astardzhiev]

Hi @MikeSangray2019 ,

Thank you for bringing this KB to my attention I was not aware of it.

As mentioned at the beginning of the KB, this is relevant in case your GP portal and GP gateway are hosted on different addresses/devcies.

Can you first confirm your setup is using diffent devices/addresses for GP portal and gateway?

[TomYoung · Accepted solution]

Hi @MikeSangray2019 ,

If your internal DNS server is also authoritative for your public domain, you have to create an internal DNS entry for the portal in order for GP upgrades to work.  Otherwise, your GP client sends the DNS query to the internal DNS server and gets nothing.  I create an A record on our internal DNS server for the same name and public IP address assigned to the portal.  It is basically a duplicate of the public DNS record, but done internally.

If your internal DNS is not authoritative for your public domain, it should forward the DNS request to the Internet and get the correct public IP address.

I have done this for myself and many customers.  I learned this through experience, not any documentation.

Thanks,

Tom