I'm sure this gets asked all the time but I can't seem to find the thread that answers my questions regarding it.
I'm currently running:
OpenVPN 2.3.9 amd64-portbld-freebsd10.1 [SSL (OpenSSL)] [LZO] [MH] [IPv6] built on Jan 5 2016
library versions: OpenSSL 1.0.1p-freebsd 9 Jul 2015, LZO 2.09
on:
FreeBSD TW-BHM-VPN 10.2-RELEASE-p7 FreeBSD 10.2-RELEASE-p7 #0: Mon Nov 2 14:19:39 UTC 2015 root@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC amd64
I can connect to the VPN just fine. Our network has a hardware firewall with the appropriate port forwarded.
Behind the firewall is our domain controller providing DNS ( 10.50.50.1 )
When connected over the VPN from home I can access any resource on the local network, but ONLY over IP, hostname lookups do not work. When attempting to nslookup anything it errors out as if it isn't getting a response from the DNS server.
Do we have to create a static route on the domain controller to point back to the default 10.8.0.0/24 VPN network in order for DNS queries to get back to the requesting client? Is that the way things are supposed to be, or is that rigged? It seems to make sense in my head but I've not seen it mentioned in any documentation on any howto or walkthrough I've come across yet.
We would prefer to keep the split tunnel if at all possible.
Including our config just in case:
port 1194
proto udp
dev tun
ca /usr/local/etc/openvpn/keys/ca.crt
cert /usr/local/etc/openvpn/keys/server.crt
key /usr/local/etc/openvpn/keys/server.key
dh /usr/local/etc/openvpn/keys/dh2048.pem
server 10.8.0.0 255.255.255.0
ifconfig-pool-persist ipp.txt
push "route 10.50.50.0 255.255.255.0"
push "dhcp-option DNS 10.50.50.1"
keepalive 10 120
cipher AES-256-CBC
comp-lzo
user nobody
group nobody
persist-key
persist-tun
status /var/log/openvpn/openvpn-status.log
log /var/log/openvpn/openvpn.log
verb 3
ALSO, I have verified that the client machine (windows 7) is has the TAP adapter at the highest order in the bind list.
