updates.uswest2.gslb.paloaltonetworks.com

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Announcements
Please sign in to see details of an important advisory in our Customer Advisories area.

updates.uswest2.gslb.paloaltonetworks.com

L3 Networker

Hi Team, 

 

Has the update server changed for dynamic updates ? updates.paloaltonetworks.com showing generic communication errors. A ping to updates.paloaltonetworks.com resolves to the address in the title, when ye change it in the config [device>setup>services>update server] connects again fine.. 

 

 

admin@TAC-HomeLab> ping source 10.10.20.1 host updates.paloaltonetworks.com
PING updates.uswest2.gslb.paloaltonetworks.com (52.37.195.67) from 10.10.20.1 : 56(84) bytes of data.

 

know about the article below, when the update server config is updates.paloaltonetworks.com won't connect, allow all from that IP, no sec profiles. 

 

https://live.paloaltonetworks.com/t5/Management-Articles/Unable-to-Perform-Dynamic-Updates-with-quot...

 

 

changing it to the one in the title connects again fine, only when ye unselect the checkbox to verify update server... 

 

 

updateError.GIForiginal.GIF

 

 

 

new one

 

newone.GIF

 

 

 

Cheers

 

Rob 

 

 

1 accepted solution

Accepted Solutions

Cyber Elite
Cyber Elite

updates.paloaltonetworks.com does not reply to ping, it is a cloud address that resolves to a server geographically closest to you, the update server FQDN itself has not changed and is still (and will always be) updates.paloaltonetworks.com 

 

 

If you're seeing generic communcations errors there might be local peering/routing or dns issues

If you connect to that sub-server the verification will fail as the server will authenticate as updates.paloaltonetworks.com but you are addressing it by it's unique FQDN

Tom Piens
PANgurus - Strata specialist; config reviews, policy optimization

View solution in original post

1 REPLY 1

Cyber Elite
Cyber Elite

updates.paloaltonetworks.com does not reply to ping, it is a cloud address that resolves to a server geographically closest to you, the update server FQDN itself has not changed and is still (and will always be) updates.paloaltonetworks.com 

 

 

If you're seeing generic communcations errors there might be local peering/routing or dns issues

If you connect to that sub-server the verification will fail as the server will authenticate as updates.paloaltonetworks.com but you are addressing it by it's unique FQDN

Tom Piens
PANgurus - Strata specialist; config reviews, policy optimization
  • 1 accepted solution
  • 2086 Views
  • 1 replies
  • 0 Likes
Like what you see?

Show your appreciation!

Click Like if a post is helpful to you or if you just want to show your support.

Click Accept as Solution to acknowledge that the answer to your question has been provided.

The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!

These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!

The LIVEcommunity thanks you for your participation!