mirror of
https://github.com/fosrl/pangolin.git
synced 2026-05-23 01:52:57 -05:00
[GH-ISSUE #3083] Private HTTP resource - Windows Client #17289
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @cdodd592 on GitHub (May 15, 2026).
Original GitHub issue: https://github.com/fosrl/pangolin/issues/3083
Describe the Bug
Please see discussion #3051 for details.
When using pangolin client V 0.10.2 (GUI version) the windows machine cannot reach private resources when on a LAN. Other devcies on lan such as MAC laptop and phone are able to access the private resouece.
Environment
To Reproduce
When i do a nslookup on windows pc it shows the following:
server:unknown
Address:IP of my internal DNS server
Non authoritive answer:
name:[domain name of resource]
address:public ip of my VPS where pangolin is running
When i do a curl from my windows PC i get 404 page not found - same error message if i try to browse to the resource via the domain
Expected Behavior
i should be able to access the private resource when the Pangolin client is running.
@AstralDestiny commented on GitHub (May 15, 2026):
If you nslookup a private resource what does it show? It should show like the ip to be 100.96.128.1 or so. Does the client say connected or registering?
@cdodd592 commented on GitHub (May 15, 2026):
When i do a nslookup on windows pc it shows the following:
server:unknown
Address:IP of my internal DNS server
Non authoritive answer:
name:[domain name of resource]
address:public ip of my VPS Server where pangolin is running
When i do a curl from my windows PC i get 404 page not found - same error message if i try to browse to the resource via the domain
When i do the nslookup on my apple MAC laptop that is able to access the private resource when usingt he pangolin client it shows the ip as 100.96.128.1
Looking at the logs i can see the following
2026-05-10 13:59:23.000 [INFO] Set DNS servers: [100.96.128.1]
2026-05-10 13:59:26.000 [INFO] Adjusted peer 1 to point to relay!
2026-05-10 13:59:31.000 [INFO] WireGuard connection to site 2 is CONNECTED (RTT: 5.2035647s)
2026-05-10 13:59:31.000 [INFO] WireGuard connection to site 1 is CONNECTED (RTT: 74.1616ms)
@LaurenceJJones commented on GitHub (May 15, 2026):
So the problem is more pointing towards that windows is not respecting the dns server change.
Have you configured an override via the network settings to point towards an internal DNS server instead of relying on DHCP from your router?
@cdodd592 commented on GitHub (May 15, 2026):
yes it seems that is the problem.
When i set the DNS in the pangolin client under primary upstream DNS server to 100.96.128.1 i get the same eg i cannot access the private http resource.
when the Pangolin client is active if i go into network settings and manually set DNS to 100.96.128.1 i am able to access the private resource as well as still access websites such as Amazon etc
What is stranger is if i disable my ethernet NIC and connect my PC to phone hotspot so it is using 4g via my phone, once pangolin client is enabled it is able to get to the private http resource fine and nslookup shows the expected 100.96.128.1 as the address
I have also tried disabling norton firewall and windows firewall incase that was causing issues and that makes no difference
@AstralDestiny commented on GitHub (May 15, 2026):
Are you populating the dns tunnel settings? or something odd?
@AstralDestiny commented on GitHub (May 15, 2026):
Ouch you have norton in 2026?
@cdodd592 commented on GitHub (May 15, 2026):
Below are the settings that i am setting in the app, these are the same across all my devices i am testing it with (windows PC, Apple MAC, android phone)
@AstralDestiny commented on GitHub (May 15, 2026):
Loz was asking if you define your local dns server via windows directly or via your router pushing the config to windows.
@cdodd592 commented on GitHub (May 15, 2026):
Router pushes it out to clients. I am running a technium DNS server on the network.
@AstralDestiny commented on GitHub (May 15, 2026):
nslookup <private resource> 100.96.128.1@LaurenceJJones commented on GitHub (May 15, 2026):
Could you enable logging within preferences, disconnect and reconnect to the tunnel and provide those logs to
laurence@pangolin.net@cdodd592 commented on GitHub (May 15, 2026):
When i do this it shows the following:
Server: unknown
Address: 100.96.128.1
Name: [private http domain]
address:100.96.128.8
@cdodd592 commented on GitHub (May 15, 2026):
@LaurenceJJones i have just emailed you the logs