DNS resolution fails after upgrading to 2.4.0
Posted: Fri Jan 06, 2017 5:45 pm
Hello-
I upgraded my Windows x64 Openvpn Community Edition software to version 2.4.0 from 2.3.14 and right away I can see that I cannot resolve hostnames within the LAN via VPN. Rolling back to 2.3.14 allows me to successfully resolve hostnames.
Here is the client script:
dev tun
persist-tun
persist-key
cipher AES-128-CBC
auth SHA1
tls-client
client
resolv-retry infinite
remote xxx.xxx.xxx.xxx 1194 udp
lport 0
verify-x509-name "FirewallServerCert" name
pkcs12 firewall-udp-1194.p12
tls-auth firewall-udp-1194-tls.key 1
ns-cert-type server
comp-lzo adaptive
passtos
block-outside-dns
I'm running the default openvpn 2.3 on our pfsense 2.3.2 firewall.
I cannot locate the appropriate changes that need to be made in order for DNS resolution to function under 2.4.0. Can someone point me in the right direction?
~Doug
I upgraded my Windows x64 Openvpn Community Edition software to version 2.4.0 from 2.3.14 and right away I can see that I cannot resolve hostnames within the LAN via VPN. Rolling back to 2.3.14 allows me to successfully resolve hostnames.
Here is the client script:
dev tun
persist-tun
persist-key
cipher AES-128-CBC
auth SHA1
tls-client
client
resolv-retry infinite
remote xxx.xxx.xxx.xxx 1194 udp
lport 0
verify-x509-name "FirewallServerCert" name
pkcs12 firewall-udp-1194.p12
tls-auth firewall-udp-1194-tls.key 1
ns-cert-type server
comp-lzo adaptive
passtos
block-outside-dns
I'm running the default openvpn 2.3 on our pfsense 2.3.2 firewall.
I cannot locate the appropriate changes that need to be made in order for DNS resolution to function under 2.4.0. Can someone point me in the right direction?
~Doug