FortiClient proactively defends against advanced attacks. Its tight integration with the Security Fabric enables policy-based automation to contain threats and control outbreaks. FortiClient is compatible with Fabric-Ready partners to further strengthen enterprises’ security posture.
Article Id 306677
Description This article describes when FortiClient does not send ZTNA traffic when using the wrong FQDN syntax.
Scope FortiClient endpoint v7.2.2.

FortiClient does not send traffic if the ZTNA rule for FQDN does not have the specific syntax.


For example:

This setting will work when setting FQDN destination host like 'test01.test.local:8000' and will be converted by ZTNA traffic and be received at FortiGate.



FortiClient will send ZTNA traffic to the destination.

The below setting will not work due to FQDN having the wrong syntax as 'test02:80' and will not be converted by ZTNA.

The FQDN 'test02' is not complete and Forticlient will not send ZTNA traffic to the destination.


A solution can be to modify it as 'test02.local:80' for example and FortiClient will accept FQDN and then send ZTNA traffic to the destination.