SSLVPN DNS Suffix

Hi guys, I did some searching and saw this question a few times, but none have really been resolved.

I'm configuring a Fortigate to have an SSLVPN so that remote users can access resources back at HQ. The SSLVPN itself seems to be working fine, I can authenticate, connect and access resources behind the firewall. However, DNS does not seem to be working as expected.

I've set both the DNS-Server and the DNS Suffix in the SSLVPN Settings:

config vpn ssl settings
    set dns-server1 192.168.1.2
    set algorithm high
    set tunnel-ip-pools "SSLVPN_TUNNEL_ADDR1"
    set dns-suffix "their.domain.com"
end

And I've also set the domain name in the system dns settings:

config system dns
    set primary 208.91.112.53 (system default)
    set secondary 208.91.112.52 (system default)
    set domain "their.domain.com"
end

When I connect to the VPN, I'm able to ping resources by IP and FQDN, but not by short name. EX: Pinging 'server.their.domain.com' works and resolves the name, but just pinging 'server' doesn't.

When I look at my ipconfig /all on windows, this is what the FortiSSL Adapter looks like:

PPP adapter fortissl:
   Connection-specific DNS Suffix . :
   Description . . . . . . . . . . . : fortissl
   Physical Address. . . . . . . . . :
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes
   IPv4 Address. . . . . . . . . . . : 10.212.1.201(Preferred)
   Subnet Mask . . . . . . . . . . . : 255.255.255.255
   Default Gateway . . . . . . . . . :
   DNS Servers . . . . . . . . . . . : 192.168.1.2
   NetBIOS over Tcpip. . . . . . . . : Enabled

So it looks like the DNS Suffix isn't being sent or properly applied? My computer is on a completely separate domain than the domain of the network the firewall protects. When I use Wireshark to look at what DNS requests are being made, I see some requests going to 'server.my.domain.com' and 'server.myother.domain.com', but of course the DNS name does not exist on those domains. I never see a request going to 'server.their.domain.com.

This may be a windows issue, but I'm not sure what steps I need to take to fix it. Anyone have any idea what's happening?