A user can open payroll.corp.example through the VPN but cannot open payroll. Confirm whether Windows expands the short name with the expected DNS suffix before investigating the tunnel.
Resolve-DnsName -Name payroll.corp.example -Type A -DnsOnly
Resolve-DnsName -Name payroll -Type A -DnsOnly
Get-DnsClientGlobalSetting
Get-DnsClient | Select-Object InterfaceAlias, ConnectionSpecificSuffix
Compare the output on a working and failing client. Check the global search list and connection-specific suffixes, including settings managed by endpoint policy or by the VPN client. A search suffix expands a short name. Split DNS determines which resolver handles a matching name. In some environments a short name can resolve to an unintended record if another suffix is tried first.
Worked example. The full name resolves to the expected application, but the VPN client lacks the approved corporate suffix. After the policy owner restores the expected suffix, the employee reconnects. Both DNS tests return the approved address. The engineer then opens the original application and confirms its hostname, certificate, and sign-in behavior.
See Microsoft’s Resolve-DnsName reference. For VPN-specific checks, see our FortiClient guide and GlobalProtect guide.