topic AD DNS Zone with A Record not resolving through GlobalProtect VPN gw in General Topics

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

PeterDanielsCRB — Wed, 01 Jul 2020 20:59:27 GMT

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

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

Remo — Wed, 01 Jul 2020 21:35:24 GMT

Hi @PeterDanielsCRB

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

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

PeterDanielsCRB — Wed, 01 Jul 2020 21:38:46 GMT

Thanks for the response, @Remo

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