FortiClient connects and the payroll application accepts TCP connections by IP, but its hostname fails. Reproduce the problem with one fully qualified domain name and the internal DNS server expected to answer it. The commands below use example addresses and a reserved domain.
Resolve-DnsName -Name payroll.corp.example -Type A -DnsOnly
Resolve-DnsName -Name payroll.corp.example -Server 10.20.0.53 -Type A -DnsOnly
Find-NetRoute -RemoteIPAddress 10.20.0.53
Read the two DNS results together. If the explicit query succeeds and the default lookup fails, check the DNS server assignment and the split DNS domain configuration for the dial-up IPsec profile. Confirm the affected user is on that profile. If both fail with a timeout, first check the route to the resolver, the FortiGate policy for DNS traffic from the VPN pool, and whether the server receives queries. If the internal server returns the wrong address, inspect the record and DNS view. Test AAAA records as well if the application uses IPv6.
Worked example. The explicit query returns 10.20.30.40. The default lookup fails because the assigned profile covers a different DNS suffix. After correcting the approved domain match, reconnect the client. Run the default query again, confirm the application opens by its intended hostname, and verify that a public domain still resolves as designed.
For cases where access by IP also fails, use the FortiClient internal-network troubleshooting guide. See Fortinet’s dial-up IPsec split DNS guidance.