internal DNS to access some of our internal services
this used to work though, and today it doest .... what could have changed?
Behind a Fortinet SSL VPN
Solved! Go to Solution.
Created on 08-01-2025 12:11 AM Edited on 08-01-2025 12:12 AM
hello, thanks for answer...
i am not sure if we switched from split tunnel to full tunnel dns,I would need to check with out IT dept, but i did fix the issue with a WSL setting
networking mode mirrored instead of NAT and now it works again for both on and off VPN
many thanks!
Hi wayneski,
go with a packet capture when a DNS query is made.
From the WSL CLI you should be able to run some commands to see who the DNS server of that virtual system is.
sudo service systemd-resolved status
or so should give that output. Did the SSLVPN change from a split tunnel DNS to a full tunnel? I would not be surprised if the WSL may not notice that and send DNS queries to its regular intended server which however no longer receives those queries.
Best regards,
Markus
Created on 08-01-2025 12:11 AM Edited on 08-01-2025 12:12 AM
hello, thanks for answer...
i am not sure if we switched from split tunnel to full tunnel dns,I would need to check with out IT dept, but i did fix the issue with a WSL setting
networking mode mirrored instead of NAT and now it works again for both on and off VPN
many thanks!
Hey,
thanks for letting us know. This might help someone else as well, you should mark your post as solved, if possible. Was there a reconfiguration of that networking mode on WSL, as it worked before?
Ok sure, marked as answer. No reconfiguration needed, just open "WSL Settings" app, go to Networking -> Networking mode and select Mirrored and restart WSL.
User | Count |
---|---|
2547 | |
1354 | |
795 | |
644 | |
455 |
The Fortinet Security Fabric brings together the concepts of convergence and consolidation to provide comprehensive cybersecurity protection for all users, devices, and applications and across all network edges.
Copyright 2025 Fortinet, Inc. All Rights Reserved.