From c7a7a7f61fd263d53fb50a85b578a180f6391b66 Mon Sep 17 00:00:00 2001 From: RamSet Date: Fri, 8 Jun 2018 18:13:57 -0600 Subject: [PATCH] Update dual-VPN.md Added sections/Titles for better page layout and reading. --- docs/guides/vpn/dual-VPN.md | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/docs/guides/vpn/dual-VPN.md b/docs/guides/vpn/dual-VPN.md index 3131343..f878028 100644 --- a/docs/guides/vpn/dual-VPN.md +++ b/docs/guides/vpn/dual-VPN.md @@ -1,13 +1,14 @@ +### Advanced use of VPN and Pi-hole If you want to run two VPN servers, one that routes the traffic and one that answers only to DNS requests, you would have to create another instance of OpenVPN. -Why would you want to do this? - +### Why would you want to do this? Because DNS is restricted to port 53 only, you cannot use it as your own DNS outside your network unless you make it public and making a DNS server a public server, is not always the best idea and it comes with some risks. So why not use the VPN tunnel to answer to DNS queries only? No traffic goes through it, except for the DNS queries, that are answered (and tracked if you have the Admin interface installed) by your Pi-hole. You can even use the same .ovpn file, with minor modifications (no need to generate it again). +### Prerequisites and Configuration We're going to use the original configuration file and copy it and then, edit the second file: sudo cp /etc/openvpn/server.conf /etc/openvpn/server2.conf sudo nano /etc/openvpn/server2.conf @@ -32,6 +33,7 @@ The next step is to edit the exisitng .ovpn file that is used for this connectio When editing the file, update the port from the provious value, to the port you set-up for the second instance of OpenVPN configuration file. +### Testing Before testing, make sure you: 1. have the port forwarded to the second instance of VPN