I have a busy Windows 2008 Server that I remotely administer through OpenVPN/RDP
Right now the OpenVPN Tap Adapter is listed first with the two physical NICs listed afterwards. The Tap Adapter only has 127.0.0.1 listed as DNS server and the physical NICs has the correct DNS servers listed.
After installing SMTP I realized that only the DNS server of the first adapter is used, which of course causes issues since this is set as 127.0.0.1
Does it matter if I just ad the correct DNS addresses to the TAP Adapter or should I rather change the adapter order. Does the fact that the Tap adapter is listed first cause any performance issues on my busy server?
OpenVPN Adapter Order / DNS issues
Moderators: TinCanTech, TinCanTech, TinCanTech, TinCanTech, TinCanTech, TinCanTech
Forum rules
Please use the [oconf] BB tag for openvpn Configurations. See viewtopic.php?f=30&t=21589 for an example.
Please use the [oconf] BB tag for openvpn Configurations. See viewtopic.php?f=30&t=21589 for an example.
-
- OpenVpn Newbie
- Posts: 1
- Joined: Mon Jan 03, 2011 1:27 am
- gladiatr72
- Forum Team
- Posts: 194
- Joined: Mon Dec 13, 2010 3:51 pm
- Location: Lawrence, KS
Re: OpenVPN Adapter Order / DNS issues
Hello,
I've never used windows as a server-side platform for OpenVPN (many, many clients, though), but I thought I'd throw in my thoughts.
I think either way sounds viable. Having the tap adapter as the "first" adapter makes perfect sense in terms of a windows vpn client, but since only openvpn and the networking stack have any business with the tap device on a server, I can't see this having any adverse effects. Similarly, adding the IP of your DNS server to the tap device sounds like it would solve the problem as well.
Regardless, I would probably duplicate your configuration on a non-production system. I would be very interested to hear how it turns out.
Regards,
Stephen
I've never used windows as a server-side platform for OpenVPN (many, many clients, though), but I thought I'd throw in my thoughts.
I think either way sounds viable. Having the tap adapter as the "first" adapter makes perfect sense in terms of a windows vpn client, but since only openvpn and the networking stack have any business with the tap device on a server, I can't see this having any adverse effects. Similarly, adding the IP of your DNS server to the tap device sounds like it would solve the problem as well.
Regardless, I would probably duplicate your configuration on a non-production system. I would be very interested to hear how it turns out.
Regards,
Stephen
[..]I used to think it was awful that life was so unfair. [...]Wouldn't it be much worse if life were fair, and all the terrible things that happen to us come because we actually deserve them? -Marcus Cole