The line push dhcp-option DOMAIN mylocaldomain.lan tells the server to send your local domain to the client as a place for it to search for hostnames that are used by not fully qualified.Īs mentioned above, the crux of the problem is that the client's nf files doesn't contain everything it needs. The line push dhcp-option DNS 192.168.1.1 tells the server to send the address of the local networks DNS server (in this case your router) to the client. In this example all local resources are at 192.168.1.XXX and all OpenVPN clients are at 192.168.2.XXX. Make sure that your OpenVPN IP pool (the server 192.168.2.0 255.255.255.0 line does not conflict with the addresses assigned by your router / DHCP server. Tls-cipher TLS-DHE-RSA-WITH-AES-256-GCM-SHA384 My server configuration file ( /etc/openvpn/nf) looks like this port 1194. I setup my OpenVPN server using a script from. My OpenVPN is running on an LXC Container hosted on a Proxmox server. Static IP addresses for LAN resources (computers) are assigned at Services -> Services -> DHCP Server -> Static Leases. Services -> Services -> LAN Domain is set to mylocaldomain.lan. 
Setup -> Network Address Server Settings (DHCP) -> Use DNSMasq for DNS is checked.My router is loaded with DD-WRT Firmware v24-sp2 (03/25/13) std.My TP-Link TL-WDR3600 router is setup as a DNS Server and DHCP Server. Run the openvpn command with -script-security 2 flag to allow update-resolv-conf to be run as in the following example sudo openvpn -script-security 2 -config /path/to/client.ovpn.Add the following 2 lines to your client.ovpn file to run update-resolv-conf every time you connect to or disconnect from your VPN server up /etc/openvpn/update-resolv-conf.
This can all be done by running the following sudo apt install resolvconf
Install the resolvconf package to give your OpenVPN client the ability to rebuild the nf file when you start and stop your VPN connection backup/remove your existing nf file and create a symlink to resolvconf's nf file. Push "dhcp-option DOMAIN mylocaldomain.lan" This tells the client that they should use 192.168.1.1 as the DNS server (typically your router's IP) and mylocaldomain.lan as a domain to sort of "automatically" append to hostnames that are requested. Ensure the following two lines are in your nf (typically at /etc/openvpn/nf). Getting these two lines added (and removed) from nf automatically is the goal. The problem boils down to the fact that, by default, the client's nf file doesn't contain a line to point the client to the VPN's DNS server nor does it contain a line telling the client what your local domain name is. Check out the rest of the article for more details on my setup.
0 kommentar(er)
