It acts as a DHCP server for the incoming (authorized) connections. Having a hard time following the trail on this one. I don't know if comodo will give me a way to disable the VPN when on our home network and reconnect it once another network is detected, but I'm trying solve problems ahead of time instead of kicking them further down the road in hopes that another package will solve them. Connecting to the wifi AFTER connecting to the VPN just breaks network connectivity. That's not especially important, as it does not need the VPN once it is on my wifi, but I intend to push this VPN config to several mobile devices via comodo MDM so that everyone has the ad/smut blocking working for them, at home or not, without user intervention. even though the hostname Jesse can be resolved by LAN and WiFi devices, including the Android that I am testing with when it is on the wifi instead of the VPN.ĪLSO, it can't connect to the VPN from inside the network. 20:10:55Ě jesse pcsupreme.vpn OK (cached) NODATA (0.4ms) A quick glimpse at the Pi Hole's recent queries list shows: For example, connecting to a web site via FQDN works fine, but connecting to a web server named Jesse fails. Hooray!īUT, I can't seem to resolve internal hostnames while connected to the VPN. The android device can connect to the VPN while it is on mobile data, and all ad/smut blocking works as it should from outside my network while using the mobile carrier's gateway. Used the openvpn-install shell script to generate an ovpn file, copied it to an android and imported it. I edited /etc/openvpn/nf on the Pi Hole and added the lines: The Pi-Hole dashboard began showing accurate per-client statistics, ad-blocking worked (pi-hole), smut-blocking worked (opendns), and DHCP clients can resolve both internal and external hostnames. I set the DNS servers on Luke and Beau to use OpenDNS forwarders of 208.67.220.220 and 208.67.222.222. I set Roscoe (Pi-Hole) to use custom forwarders of 10.0.1.2 and 10.0.1.3 (Luke and Beau). I went into Luke's DHCP server settings and told it to hand out 10.0.1.15 (Roscoe, the Pi Hole) for the DNS server. So I ran with my second-to-last paragraph above. That way I would have more accurate client information in the Pi Hole admin console and local devices would not be bypassing the Windows DNS servers, even if they are connected to the VPN.Īssuming the last paragraph above is a viable solution (I'd love to hear potential problems and alternative ideas if it is not), how to do need to configure my nf and client.ovpn files? Instead of having Luke and Beau forward external queries to the Pi Hole (which then forwards them to OpenDNS), I was thinking I would change the DHCP server (Luke) to send clients the Pi Hole as the DNS server, have it forward queries to 10.0.1.2 and 10.0.1.3, and then have them forward queries to OpenDNS. ovpn file? Input appreciated there.Īlso, when the VPN clients are local, they need to be able to use the Windows DNS servers for local hostname resolution, which the VPN config bypasses. I made the change suggested here and it broke internet access for the VPN clients. The content and ad filtering is still working, but it is using the office gateway and I only want DNS queries going over the VPN. I set up the OpenVPN server on the Raspberry Pi and tested using an Android device that was on mobile data. The problem is that the howto doesn't consider use cases like mine where there are actual DNS servers on the local network that clients need access to when they are local. Setting up my DNS as WAN-facing comes with the obvious security vulnerabilities, so I took a look at the docs on using OpenVPN and liked what I saw. I REALLY want devices outside of the network to also use the Pi Hole and OpenDNS. It all worked great, except that the Pi Hole dashboard was only showing query information for two clients (Beau and Luke) instead of the actual client machines.

To start off and establish a proof of concept, I set up Pi-Hole on a Paspberry Pi 3 and configured it to forward external queries to OpenDNS, then changed the Windows Servers to forward queries to the Pi-Hole (Roscoe 10.0.1.15), essentially placing the Pi Hole between my internal devices and OpenDNS to perform its sinkhole duties. Previously, both zones were using OpenDNS as forwarders for external queries. I have two Windows Server 2016 machines running the DNS role in my house, as primary and secondary DNS Zones (Luke 10.0.1.2 and Beau 10.0.1.3). This is a (relatively) simple configuration question, so I hope I am asking it in the right place.

Opendns updater raspberry pi