Wireguard VPN and accessing internal DNS server

Bluecube

Bluecube

Bluecube

Soldato
Joined
20 Feb 2011
Posts
4,233
I've been using Wireguard to access my home network for years now and it's been great. One bugbear is that to access internal resources I've always had to type in the IP address rather a friendly URL. I know it's a DNS issue but I've idea how to rectify it despite googling and many hours of fiddling. Can anyone point out what I've been missing?

I don't think it makes much difference but I'm currently running Wireguard on a UDM. Previously it was on Unraid. The issue persists across the platforms.
 
Does the UDM run a DNS server that you can configure, or does it just allocate DNS hosts to DHCP clients? Are you even resolving these addresses through DNS as opposed to NetBIOS?

If you open a command prompt on your PC and type in "nslookup [name of host]" e.g. nslookup nas then what comes back?
 
I'm using a Mac if that makes any difference. Typing in Nslookup returns NXDOMAIN.

Thanks for all the info. Networking is a real weak spot in my IT knowledge and I didn’t realise there were so many different nuances to DNS. I thought I was running a DNS server on either my UDM or Adblock server but these don’t resolve local DNS names from what I can see and experience. I’ll look into this further but I think I need a ”proper” DNS server to resolve local addresses to hostnames and point WireGuard at it.
 
With the UDM and VPN you are on a different network subnet to your primary LAN, yes you've got the interVLAN allowed but your Network is 192.168.2.x and LAN maybe 192.168.0.x so that routing table wont see those devices until you add the DNS entry or ping it. You could try the Name Server option on the VPN/WireGuard side and use the primary LAN DNS as Entry 1 and WG subnet as Entry 2.
 
You must log in or register to reply here.
Back
Top Bottom