Yes, we have an internal DNS server on the LAN.
OK, step 1 is to confirm the internal DNS servers are assigned to the client under: Network> LAN> DHCP Server. Uncheck “Assign DNS server automatically” to configure the internal DNS severs.
For step 2 which model router are you using for OpenVPN? Special firmware may be needed for this, so please let us know the router model and firmware version.
1 Like
The Assign DNS server Automatically, was already unchecked, and the correct DNS server IPs are configured in the DNS server 1 & 2 settings.
We are using a Peplink Balance One, with firmware 8.0.2 installed.
We have the same problem with our Peplink 710, was there a resolution to this?
When our OpenVPN client connection establishes, the DNS server specified in the DHCP server does not get allocated to the VPN adapter. We get the Peplink LAN IP as our primary DNS and users cannot access devices on the LAN by their host name.
Unfortunately, there was no resolution to this issue as of yet.
My OpenVPN client has no problem to grab the customized DNS IP as @Ron_Case suggested. The customized DNS server is used when I do DNS lookup. Please find the screenshot below.
Please ensure you are using the latest firmware version.
1 Like
I am having the same issue and it seems to only happen on the VPN VLAN “51”. It does not apply DNS or WINS so I have had to set them manually for each adapter in Windows. Any idea how we resolve this?
It only seems to be a problem if you are using a VLAN on my end.
@Gavin_Pitt, I don’t have the problem to grab custom DNS IP addresses in VLAN 51. I am using firmware version 8.0.2.
1 Like
Well that is odd. I am running firmware 8.0.2 as well and this certainly does not work. Any idea what I can check? Troubleshooting steps?
Which device in the VLAN 51 is holding the IP address 192.168.51.254 ? Base on the screenshot shared, it’s the DHCP server for your device now. You have 2 DHCP server running for your network ? This is not a recommended setup as you won’t able to control with DHCP server going to assign the DHCP IP to the client devices.
1 Like
I have a Windows server running DHCP on the 192.168.50.* range but it is not on the same VLAN. If I try and connect OpenVpn without DHCP Enabled on the Peplink it does not connect at all.
@Gavin_Pitt, this is interesting. Please open ticket and turn on Remote Assistance for me to take a closer look. Please attention the ticket to me.
Thanks.
1 Like
Ticket has been created #20040028
Any update on this issue? I’m running into the same thing on a similar domain structure.
If I update the DNS entry for the Open VPN virtual adapter and define the DNS it works fine.
They sent me a specific firmware update for my device which resolved the issue.
Thanks for the update. I’ll probably end up waiting for the next version release, since i’m sure it’s something that will be fixed in a regular update. I only have a few devices this is a problem with, but I wanted to investigate it now since we are expanding remote access and locations.