[BUG] Internal domains not accessible in wireguard mode

[725525]

⚠️ Before submitting:

• I have checked the existing issues to ensure this is not a duplicate.
• I have updated BlockAds to the latest version available on GitHub.

This issue is the follow up on #129

Hi thanks for the release, just tested it and it is still not working. My configuration

• Wireguard server ip: 10.8.0.1 (this is also the wireguard dns address)
• Wireguard client ip on blockAds: 10.8.0.4
• Internal domain hosted in 10.8.0.1 --> mymango.com and web.mymango.com
• Added them in split dns zones
• Still unable to connect to internal domains

P.S. this works fine in standalone Wireguard app.

[nqmgaming]

Thanks for reporting. I found the root cause.

How Split DNS is supposed to work:
When you add zones like mymango.com in the Split DNS field, queries for mymango.com and web.mymango.com should be resolved via your WireGuard DNS (10.8.0.1) instead of the upstream DNS.

The bug:
BlockAds excludes its own app from the VPN (addDisallowedApplication). This means ALL traffic from the app — including split DNS queries — bypasses the VPN tunnel. So when the resolver tries to reach 10.8.0.1:53, the packet goes through the regular internet instead of the WireGuard tunnel. Since 10.8.0.1 is only reachable via WireGuard, the query fails.

Working on a fix — need to forward split DNS queries through the WireGuard tunnel directly in the Go engine instead of using a socket.

[725525]

Thanks for looking into this. How about:

• Have an option (like a checkbox in UI) to optionally route all traffic via wiregurd dns in wireguard mode (full tunnel)
• This will be in addition to split tunnel feature you implemented earlier
• The backend system should then: only forward internal domain if route-all-traffic-via-wireguard is unchecked, and forward all queries via wireguard dns when that option is checked.

[725525]

FYI: In the current version, if I use 10.8.0.1 as custom dns in UI, it cuts off the internet.