GlobalProtect DNS server ignores the access routes

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.

GlobalProtect DNS server ignores the access routes

L4 Transporter

Hey all,

Just another PaloAlto funkiness I found out today...

When you configure a DNS server under the gateway configuration for GlobalProtect a route will automatically be added to route traffic to this DNS-ip through the tunnel: REGARDLESS of what you fill in in the access routes.

Ex: DNS server: 10.0.0.1 and access route: 192.168.0.0/16

When connected with GlobalProtect your Windows route table will be

192.168.0.0/16 -> GlobalProtect tunnel

10.0.0.1 -> GlobalProtect tunnel (although this ip is NOT in the access route range)

Just something to think about when you are maybe running into routing issues like I was.

1 accepted solution

Accepted Solutions

Cyber Elite
Cyber Elite

when we add the x.x.x.x/32 access route for the DNS server we also ensure this DNS server will always be reachable for clients, even if they are located in a network that overlaps the access route and possibly have a local resource with an identical IP (/32 has priority over all bigger subnets), or the access routes inadvertently don't cover the DNS' IP

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

View solution in original post

2 REPLIES 2

L7 Applicator

Thanks for the note.

I guess this make sense since you would need a route to use the DNS server.  So we would be adding a subnet for this route for the clients during the setup process.

But I'm with you, I like to have independent control of where the routes are installed on the network.

Steve Puluka BSEET - IP Architect - DQE Communications (Metro Ethernet/ISP)
ACE PanOS 6; ACE PanOS 7; ASE 3.0; PSE 7.0 Foundations & Associate in Platform; Cyber Security; Data Center

Cyber Elite
Cyber Elite

when we add the x.x.x.x/32 access route for the DNS server we also ensure this DNS server will always be reachable for clients, even if they are located in a network that overlaps the access route and possibly have a local resource with an identical IP (/32 has priority over all bigger subnets), or the access routes inadvertently don't cover the DNS' IP

Tom Piens
PANgurus - Strata specialist; config reviews, policy optimization
  • 1 accepted solution
  • 2110 Views
  • 2 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!