Forticlient changing DHCP assigned DNS to static

[rmnetops]

We are using Forticlient 4.2.4.0271 Recently we started noticing that Forticlient changes a DHCP assigned DNS setting on the NIC to a static DNS setting while it is connected (and uses the DNS settings of the IPSEC VPN connection from a Fortigate as the static settings). It then changes it back to automatically assigned when the Forticlient is disconnected. However, if the system goes into hibernate while the Forticlient is connected, it doesn' t seem to revert these DNS setting changes back to DHCP automatically assigned, causing an issue when the user tries to use the Internet on another network that requires DHCP assigned DNS. Has anyone else seen this problem?

[Jakob-AHHG]

So, this seems to still be an issue on Win11 / FortiClient 7.07.xx
But it's only on Windows.
On Mac OS X, FortiClient does not mess with network interfaces, other than the VPN interface.

Why is FortiClient on Windows f*ing with the interfaces?!?

[karateko45]

This is insane. It's one of the worst VPN implementations I have seen.

[Jakob-AHHG]

To my understading, it seems to be an issue with Windows.. but not sure.

[LVNVScott]

We use FortiClient in conjunction with FortiSASE to provide remote access. However, this issue continues to occur frequently on client version 7.2.9.1185. It’s particularly disruptive for end users, as they lack the permissions to revert the DNS settings themselves—and once affected, we’re unable to access their machines remotely to assist. This needs to be addressed urgently. Ideally, the client should include a startup health check that automatically restores any DNS settings it previously modified.