02-16-2022 02:08 PM
Hello,
We have a use case in which we have say example.com resolving internally(on-prem) to 10.1.1.1, this will resolve internally while you are connected to the corporate network using the corporate network DNS servers. the global protect clients are also pointed to the internal corporate DNS servers. So all the traffic for DNS comes through the GP tunnel.
As soon as we created an external DNS entry for the same example.com to resolve to 111.111.111.111 publically. Linux endpoint users even while they are connected to GP and are using corporate DNS servers, the name resolution for example.com resolves to the public IP and not the private one the issue seems to be intermittent and is affecting multiple clients, This setup does not affect mac or windows clients who use the same internal DNS server over GP VPN.
Has someone come across this scenario before? Any help is appreciated.
06-02-2023 05:15 AM
'mangle' table from 'OUTPUT' chain, 'nat' table from 'POSTROUTING' chain and all the corresponding rules when VPN connection is up may provide an idea on what is going on. There is a play with DNS.
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!
