AD DNS Zone with A Record not resolving through GlobalProtect VPN gw

Reply
Highlighted
L0 Member

AD DNS Zone with A Record not resolving through GlobalProtect VPN gw

We are using Active Directory for our internal corp DNS.  I am connected to the corp network using GlobalProtect VPN (multi-gateway).  I'm able to resolve names in our primary DNS zone across the VPN tunnel.  I just added a new zone, which overrides a public zone - database.windows.net.  And, I added an A record to it: <myHostName>.database.windows.net.  When I am on a server in eth corp network, the A record resolves using the FQDN.  However, from my laptop, using the VPN gateway, the DNS does not resolve to eth internal A record IP.  It resolves to a public IP.

 

How do I tell GlobalProtect to make that DNS zone and the A record available to clients connecting vi VPN gateway?

 

Yes, I'm a total GlobalProtect noob.  I will be passing this info on to our network peeps to config the gateways (hopefully). Thank you!

 

-Peter

Highlighted
Cyber Elite

Hi @PeterDanielsCRB 

Are the same DNS servers used on a client connected by global protect and your internal server?

Highlighted
L0 Member

Thanks for the response, @vsys_remo 

 

They seem to be different, yet somewhat sync'd - at least the main company zone (domain) seems sync'd.

 

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 Live Community as a whole!

The Live Community thanks you for your participation!