Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Local DNS Server (through Wireguard) just won't work #1842

Open
skisbit opened this issue Jan 15, 2025 · 1 comment
Open

Local DNS Server (through Wireguard) just won't work #1842

skisbit opened this issue Jan 15, 2025 · 1 comment
Assignees

Comments

@skisbit
Copy link

skisbit commented Jan 15, 2025

Hello, I want to start by saying that I've read similar issues but I haven't found any answer or solutions for this problem, so I resort to opening a new issue. Sorry if it's a bad move.

The issue:
The app works fine for me with the exception of local domains through the Wireguard tunnel. When the app is active the traffic is routed through the tunnel and I can access different home-servers using their IP-address. But when I use their domain-name I only get the same error as if accessing the domain without a VPN.

The configuration:
I have configured the Wireguard VPN to have the correct DNS server, and I use the simple mode, as it is to my understanding that it's the only way to implement the Wireguard DNS option. When I start up the tunnel in the app I can see that the DNS module selects Wireguard as its source.

The tunnel configuration works well in other wireguard tunnel apps. I can provide further technical details if necessary, if there isn't a known fix.

@ignoramous
Copy link
Collaborator

Are you using WireGuard in Advanced mode or Simple mode? If the former, DNS isn't routed to WireGuard-configured DNS server in v055n & lower. v055o will have the capability to do per-app per-WiregGuard DNS resolution for A/AAAA (IPv4/IPv6) records.

If the latter, can you check:

  1. Configure -> Logs -> swipe to "DNS" tab
  2. Search for the local domain
  3. Tap on the entries that show up
  4. In the bottomsheet that comes up, see if there's any error msg in the footer or the name/address of the resolver which is shown just below the "answer".

@ignoramous ignoramous self-assigned this Feb 12, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants