Hi there,
When I set a service using DNS as a host is not possible connect, but when I changed the host by IP destination works fine.
On ZTNA server works with IP or host the problem occurs on the worktations over tunnel, but not for all service some works with DNS.
Details activity when fails:
When you create a service,
if you set destination as a hostname (not ip), please check on ferrumgate machine to ping $hostnamethatyouentered, (check also if ipv4 is resolved)
If you enter an ip as destination, please check ping $ipthatyouentered
Then on the client, after connected to ferrumgate successfuly
please check ping $servicename
if both of them works, please check Policy/Authorization rule
Hi
On ferrumgate machine I can ping hostname and resolve with an IPv4
On client when I set any services I can ping even and the Policy/Authorization rule is OK because when I change the hostname to IP on service I can connect.
when setting service target to hostname, there could be a bug about resolving. I will check it
Hi, did you have time do check this, pls?
Yep, we are working on a new version. I will check this also. Please follow new version release