Adguard not working with VPN

Hello,

i have VLAN based VPN client activated on my Marble router. When activating Adguard Home, at first everything seems to work. My private VLAN clients access internet normally and the guest VLAN clients access internet over VPN.

When i look on the Adguard Home Web UI there are no DNS requests though. I also activated VPN DNS server as upstream DNS in Adguard for guest VLAN.

In my understanding guest clients should use adguard but use VPN DNS server and VPN should work (which it does). Private clients should just use adguard dns but this seems not to work. When disabling VPN, Adguard immediatelly gets DNS requests.

Any idea how to fix this?

Best regards

Andy

Hi

Please try upgrading the firmware version to latest beta version 4.7.15 and enabling the option: Network → DNS → Allow Custom DNS to Override VPN DNS.

The latest firmware can be download here and you can upgrade it according to this guide.

Oh nice. That’s actually a nice feature you implemented. Although somehow it works since today morning. I did not change anything since yesterday, but it is still working now. VPN is working without leak and normal traffic goes through Adguard.

For now i will not upgrade to beta version, but still good to know there is a new feature coming.

I have to correct myself, something is strange. Everything is fine with VPN. My Guest VLAN is using custom upstream DNS, i have no leaks and i'm recognized in the correct country.
But the normal (private) VLAN is odd. The requests are processed by Adguard, but DNS leak test shows a server from different country (VPN location). Upstream DNS is quad9, so i guess the nearest quad9 is used. But why the VPN location? My private VLAN should not use VPN.
After setting the global upstream DNS to my local ISP Router dnsleak shows the correct server in home country.

As I was curious about the beta version, I installed it. So above scenario is on both versions. Besides from that i really like the update, good work here :+1: The relationship between VPN and Adguard is odd, though.

Best regards

At the moment, the VPN policy mainly applies to client (LAN/Wi-Fi) traffic.
Part of services that run directly on the router itself—such as AdGuard Home—will still use the VPN connection.
That’s why you’re seeing this behavior.

I understand, that explains the behaviour. I think my workaround here would be an additional router for VPN or installation of Adguard Home on a seperate machine (e.g. Raspberry). An internal seperation from VPN and Adguard in the future would be nice, though.

Thx for your help.

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.