Forticlient on Mac not resolving host name after upgrade to Ventura

[Ola]

Hello,

since our users upgraded to Ventura on their Macs, when connected to the Forticlient vpn app, they are not able to get to any internal website using hostname - the vpn is not recognising the hostname and not resolving it.

anyone come across this issue and has anyone got a fix for it? we are currently on 6.46

thanks

[distillednetwork]

There was a bug for Forticlient mac related to DNS resolution that was fixed in 7.0.7

790733

FortiClient cannot resolve DNS suffix after connecting to SSL VPN.

https://docs.fortinet.com/document/forticlient/7.0.7/macos-release-notes/510031/resolved-issues

Also, are you setting the DNS suffix on the SSL-VPN settings in the fortigate?

https://community.fortinet.com/t5/FortiGate/Technical-Tip-How-to-set-DNS-suffix-for-VPN-SSL-and-IPse...

[Ola]

Hello,

yes the dns suffix is set on the ssl-vpn in the FortiGate.

the thing is everything worked before the upgrade and still works for those that haven't done the upgrade

[distillednetwork]

Is 6.4.6 the version of FortiClient VPN you are using or the version on the Fortigate?  

If its the Fortigate, what version of Forticlient do you have installed on the mac?

[Kubus]

Did you get this resolved? We are still experiencing the same problem even with the latest VPN client

[Ola]

unfortunately No. and not had much help from Forticlient really, just a merry go round, the temp solution has been to push out a manually dns address to the devices which allow this to work