soulseeker
Hi there,
first of all - we are using a watchguard-openvpn-client, that is based on openvpn, just labled different.
Since we are using it, we frequently run into DNS issues.
The first issue - domain joined workstations have troubles identifying the network interface of the tap driver. With this unidentified network the clients can't resolve dns. I can only solve this problem by adding an additional gateway in the tap driver. This is really annoying, because I have to repeat this step everytime the watchguard client get's an update. This often causes troubles because most of our users don't have local admin rights. But after adding the gateway manually the name resulotion always works for my domain joined clients.
Second problem - today I got a slightly different dns issue on a freshly installed windows 10 client from my home office. This client is not domain joined.
The clients connects fine, gets all the routes on the tap adapter, the vpn adapter gets on top of all bindings, but it doesn't query the dns server of my domain, but always my local dns. And again - name resolution of internal ressources by FQDN does not work. I tried adding the gateway manually, reinstalled the client as administrator, cleared the dns cache and so on. I can ping and RDP the remote networks' dns server IP but if I do nslookup someserver.domain.int it always "asks" my local dns (although the tap interface is on top of the binding).
Even more strage - if I ping someserver (netbios name) - it resolves to someserver.domain.int and I get an answer. But I can only RDP to "netbios name", not "FQDN". And ping someserver.domain.local prompts "host not found".
We also use a second domain with a trust for developing purposes (our main dns has got a stub zone for that domain) - when I do a ping on that with FQDN (someserver.develop-domain.int) I get an answer immediately, can also RDP with FQDN. But nslookup someserver.develop-domain.int again queries my local router.
I don't know if this is windows 10 related but with windows 8.1 (my second workstation here) I can still connect and it queries the correct dns. But by the way - a colleague with a windows10 surface tablet (not domain joined) just installed the client, connected and had no issues at all from his home wlan:(.
I already opened a ticket at the watchguard support, but they finally told me - it's not their issue, but windows related.
What I did not so far - use the native OpenVPN-client with a watchguard profile. Will that be worth a try?
Sorry for posting a watchguard issue on that forum, but maybe somebody here knows about this problem. It seems so random.
Regards
Marcel
