Local DNS when connected via the Wireguard VPN server

Follow

Didier Malenfant

• December 29, 2025 05:18

I have a Gold SE firewall with the Wireguard VPN server enabled.

When I connect to my local network via the VPN (I'm on Linux), it doesn't look like the local DNS entries are shared with my client.

I'm just trying to ping `<device name>.lan` but get `ping: <device name>.lan: Name or service not known` in return. This, of course, works fine when I'm on my local network behind the firewalla.

0

• 

  David Koppenhofer

  • December 29, 2025 07:20

  Make sure "block IMCP" is off for the network you're pinging, and make sure the Wireguard network/device has access to the ping destination/network.

  0

  Comment actions Permalink
• 

  FirewallaSupportDesk

  • December 29, 2025 07:29

  Could you try to ping the IP first to make sure the traffic is allowed? 
  
  As well as David's advice to check "block IMCP" is off on the LAN and WireGuard Interface: Box Main page -> Network -> LAN/WireGuard interface

  0

  Comment actions Permalink
• 

  Didier Malenfant

  • December 29, 2025 19:02

  Sorry I should have been more precise.

  Yes. Pinging the device's address directly does work and the device is otherwise totally accessible using it's IP address.

  In Unix if the pinging itself was the issue I would see something like:

  `PING <device name>.lan (192.168.x.x) 56(84) bytes of data.`

  and no more data after this. The fact that I don't see this indicates that something is going wrong with the name resolving BEFORE the ping is even attempted.

  For completion-sake, this issue is for any device on my local network but as I said only when I connected to the network via the VPN. When I'm physically on the local network at home the local DNS works fine.

  0

  Comment actions Permalink
• 

  Didier Malenfant

  • January 08, 2026 19:46

  Any ideas?

  0

  Comment actions Permalink
• 

  Firewalla CM

  • January 08, 2026 20:26

  Can you try an nslookup to see if your host is overriding the DNS server? And when you're on WireGuard, do you have any privacy-related DNS settings enabled? (Some settings can be SSID-specific)

  If you're using a modified WireGuard config file, you could also try to create a new client with a fresh config file.

  Let me know if any of these tips help. We can also open a case for you so our engineers can take a closer look.

  0

  Comment actions Permalink

Please sign in to leave a comment.