Help Configuring TorGuard VPN with AdGuard Home on Slate AX

Hello everyone,

I recently purchased the Slate AX router to complement my current setup. I cannot modify the settings on my ISP-provided router, so I bought the Slate AX to configure it with TorGuard VPN (with a dedicated IP) and AdGuard Home for network-wide ad blocking.

My Setup:

ISP Router: Cannot be modified.

Slate AX: Configured as a secondary router connected to the ISP router.

TorGuard VPN: Configured with OpenVPN/WireGuard, using 1.1.1.1 as the DNS server from the TorGuard config file.

AdGuard Home: Enabled and working on the Slate AX.

Questions:

  1. DNS Settings:

• Should I use 1.1.1.1 (Cloudflare DNS) as configured in the TorGuard VPN config file, or should I replace it with the Slate AX’s local router address (192.168.8.1)?

• What is the best way to ensure that AdGuard Home filters all DNS requests while still routing everything through the TorGuard VPN for privacy?

  1. AdGuard Home Message:

• I keep seeing the following message in the DNS settings of the Slate AX:

“AdGuard Home is enabled and this router will use the DNS server provided by AdGuard Home as the custom DNS server. The DNS server settings will not work.”

Can someone clarify what this means for my DNS settings and how to manage upstream DNS servers effectively?

  1. Optimal Settings:

• What are the best settings to use in the Slate AX to ensure:

• AdGuard Home filters all DNS requests.

• TorGuard VPN handles all traffic, including DNS, without leaks.

• Should “Block Non-VPN Traffic” be enabled, and how does it interact with AdGuard Home?

Additional Context:

• I want to ensure no DNS leaks and complete ad-blocking across all devices in my network.

• I use the VPN for privacy, a dedicated IP, and bypassing regional restrictions.

I’d appreciate any insights, best practices, or step-by-step guides for this configuration. Let me know if I need to provide additional details.

Thank you!

Mike

Please refer this guide to setup the VPN client with the profiles from the TorGuardVPN:

Regarding this point, and combined with your mention below, AGH should have enabled 'AdGuard Home Handle Client Requests', and then the DNS request will go to the AGH DNS (from AGH page -> DNS setting).
Thus, there is no need to change the DNS IP of the VPN client profile since the DNS requests did not go to profile 1.1.1.1, but AGH DNS.

Enable the Killswitch 'Block Non-VPN Traffic'. The VPN client will handle all traffic including DNS, but DNS requests use the DNS server in AGH if AGH is enabled.

Here is a reminder to let you know that when you enable AGH, the DNS server is assumed by ADH. Any DNS config you want, please go to AGH.

Now all of your network traffic will go through a VPN which is secure and not leak.

Thank you, bruce, for your detailed and helpful response. I appreciate the insights and guidance!

1 Like