VPN client and Google domains
-
Ok so check what the clients are using for DNS. It would normally be the pfSense LAN IP address.
Check what DNS servers pfSense is using in Diag > DNS Lookup.
If you set Unbound to localhost did you also set it to forwarding mode?
Is the VPN client setting itself as the default route when it connects?
-
@stephenw10 said in VPN client and Google domains:
Ok so check what the clients are using for DNS. It would normally be the pfSense LAN IP address.
Check what DNS servers pfSense is using in Diag > DNS Lookup.
If you set Unbound to localhost did you also set it to forwarding mode?
Is the VPN client setting itself as the default route when it connects?- Client using pfSense LAN IP
- Pfsense using 127.0.0.1 as DNS server
- Negative, Unbound not in forwarding mode
- Default route gateway is my ISP gateway if talking about System/routing settings
-
-
-
Ok, then Unbound is going to using the default route for resolving which is directly via the WAN and not via the VPN. Unless your VPN wasn't connected when you checked that?
So I would expect a DNS leak test to show the WAN IP and not the VPN.However it should still be able to resolve google via either route. You might try turning up the logging level in unbound and check for errors.
Did this just start happening?
-
@stephenw10 I don'
t have any leakages and don not see any errors in log
-
-
@stephenw10 VPN all time was connected
-
Ok, then your default route must switch when the client connects. Which is expected with the gateway set to automatic like that if the OpenVPN config doesn't expressly prevent it.
However Unbound should still be able to resolve via either route.You probably need to turn up the logging level further to see query level logs.
You might try disabling IPSec and see if that allows it to resolve though.
Steve
-
@stephenw10 Solved by set in firewall rule( Lan traffic to ExpressVpn) default gateway to ExpressVpn. Thank you for your assistance. Have a good weekend!
