On my personal computer, I can only ping hostnames using the FQDN when using version 3.2.3 and version 2.7.1. Yet I am able to ping hostnames without the FQDN when using version 2.5.1.
However, one of my field co-worker's computer can ping hostnames without using the FQDN when using version 3.2.3. Sadly, they can't ping hostnames without using the FQDN when using version 2.5.1. I didn't try version 2.7.1, since version 3.2.3 worked.
What is the cause of the inconsistencies? Is it the network or is it the computers?
My concern is that my field co-worker will go on to a different network and DNS won't fully be working. I don't want to keep switching client versions simply because they connect using different networks.
Both of these computers are running Windows 10.
[Sloved] OpenVPN client inconsistencies with DNS
-
- OpenVpn Newbie
- Posts: 3
- Joined: Fri Apr 09, 2021 7:09 pm
[Sloved] OpenVPN client inconsistencies with DNS
Last edited by TheShadow on Sat Apr 10, 2021 12:06 am, edited 1 time in total.
-
- OpenVpn Newbie
- Posts: 3
- Joined: Fri Apr 09, 2021 7:09 pm
Re: OpenVPN client inconsistencies with DNS
I fixed it. I had to update my home computer to 21H1.
-
- OpenVpn Newbie
- Posts: 3
- Joined: Fri Apr 09, 2021 7:09 pm
Re: [Sloved] OpenVPN client inconsistencies with DNS
I spoke too soon. It stopped working with version 3.2.3. So I had to go back to version 2.5.1.