Skip to main content
Felix1213
Felix1213
Explorer II
May 23, 2025
Solved

Split DNS not installed on Fedora by FortiClient

  • May 23, 2025
  • 1 reply
  • 1687 views

Hello,

 

I have split DNS configured on Fortigate for multiple SSL-VPN portals, and it working for everyone running Windows, MacOS, and Ubuntu.

It was also working for me running Fedora with Gnome, and the default NetworkManager and systemd-resolved.

 

But since not long ago it's not working anymore for me (it's still working for non-Fedora users).

It might be since I upgraded FortiClient using forticlient_vpn_7.4.3.1736_x86_64.rpm but I'm not 100% sure.

The FortiClient before the upgrade has been installed using forticlient_vpn_7.4.0.1636_x86_64.rpm.

The FortiGate appliance we connect to is running 7.2.11.

 

I can workaround by using a NetworkManager dispatcher script like this:

cat << 'EOF' > /etc/NetworkManager/dispatcher.d/at-fctvpn-connection.conf  #!/usr/bin/env bash   set -eu   # Log when there is an event echo "Receive event from ${DEVICE_IFACE:-dummy} ${NM_DISPATCHER_ACTION:-dummy} " >> /tmp/dispatch.log   # Configure split DNS if the event is Firewall VPN going up [[ "${DEVICE_IFACE:-dummy}" =~ "fct" ]] && [[ "${NM_DISPATCHER_ACTION:-dummy}" = "up" ]] && { resolvectl dns "${DEVICE_IFACE}" "192.0.2.1#dns1.example.com 192.0.2.2#dns2.example.com" resolvectl domain "${DEVICE_IFACE}" int.example.com } >> /tmp/dispatch.log  EOF  chmod +x /etc/NetworkManager/dispatcher.d/at-fctvpn-connection.conf

 

Although I'd like it to be fixed for good, or know if the issue is on my side.

Does someone have the same issue with Fedora? Or know where it is coming from?

    Best answer by AEK

    I agree that something has been changed in Fedora.

    Then I think your script is the best workaround in such situation, till Fortinet releases a new FCT version that works 100% fine on F42.

    1 reply

    AEK
    SuperUser
    AEK
    SuperUser
    May 25, 2025

    Hi Felix

    Is it possible to back to 7.4.0 and see if the issue is the same?

    AEK
      Felix1213
      Felix1213Author
      Explorer II
      May 26, 2025

      Hi, I just tried and it's not working either.

      So it's not working on Fedora anymore, it's not a regression of 7.4.3 version.

      I upgraded F41->F42 a few months ago, and I upgrade my packages on a daily base. I'm not sure what have been the trigger then.

      AEK
      SuperUser
      AEKAnswer
      SuperUser
      May 26, 2025

      I agree that something has been changed in Fedora.

      Then I think your script is the best workaround in such situation, till Fortinet releases a new FCT version that works 100% fine on F42.

      AEK
        Terms & ConditionsAccessibility statement