mirror of
https://github.com/pi-hole/pi-hole.git
synced 2025-01-26 06:19:52 +00:00
Fixed some errors and typos in the guide
parent
66f7008d47
commit
b060a844a0
1 changed files with 11 additions and 11 deletions
|
@ -6,18 +6,18 @@ This can probably replace the DNSCrypt page, but leaving it for archive purposes
|
|||
|
||||
## Step 1: Install DNSCrypt-Proxy
|
||||
|
||||
* `mkdir -p /dnsproxy`: (this is just a folder to store everything. Pihole instructions have this on the root of the partition, but should work from anywhere), suggest opt or etc.
|
||||
* Download [latest](https://github.com/jedisct1/dnscrypt-proxy/releases/latest) pre-built binary. I'm using Pi-Hole, so I used `linux_arm`. There is a binary for arm.
|
||||
* `tar -xf <dnscrypt-proxy-linux_arm-XXX.tar.gz>`: extract prebuilt binary
|
||||
* `cp dnscrypt-proxy-linux_arm-XXX.tar.gz dnscrypt-proxy`: rename the extracted folder
|
||||
* `rm -r dnscrypt-proxy-linux_arm-XXX.tar.gz`: rename the extracted folder
|
||||
* `cd /opt`: Move to /opt directory. This is where we will place the dnscrypt-proxy files.
|
||||
* Download [latest](https://github.com/jedisct1/dnscrypt-proxy/releases/latest) pre-built binary. I'm using Pi-Hole on ARM architecture, so I used `linux_arm`. Replace with your system architecture.
|
||||
* `tar -xf dnscrypt-proxy-linux_arm64-2.0.8.tar.gz`: Extract prebuilt binary
|
||||
* `mv linux-arm64 dnscrypt-proxy`: Rename the extracted folder
|
||||
* `rm dnscrypt-proxy-linux_arm64-2.0.8.tar.gz`: Remove the archive
|
||||
* `cd dnscrypt-proxy`: cd into extracted dir
|
||||
* `cp example-dnscrypt-proxy.toml dnscrypt-proxy.toml`
|
||||
* `cp example-dnscrypt-proxy.toml dnscrypt-proxy.toml`: Create a configuration file based on the example one
|
||||
* `sudo nano dnscrypt-proxy.toml`: Edit the toml file. This is where all the fancy configuration happens.
|
||||
* Edit port to be something other than `53` (since `53` is being used by Pi-Hole). This is the `listen_addresses` line. Change both IPv4 and IPv6 as desired.
|
||||
* Edit other settings as desired. I set `require_dnssec` to be `true`. There are a lot of other options, but server selection and more is already done.
|
||||
* `dnscrypt-proxy -service install`: install dnscrypt-proxy service
|
||||
* `dnscrypt-proxy -service start`: start the new service
|
||||
* Edit other settings as desired. I set `require_dnssec` to be `true`. There are a lot of other options, but server selection and more is already done. If you want to specify the server(s) you want to use, look at [this site](https://dnscrypt.info/public-servers).
|
||||
* `./dnscrypt-proxy -service install`: install dnscrypt-proxy service
|
||||
* `./dnscrypt-proxy -service start`: start the new service
|
||||
|
||||
You can see dnscrypt-proxy 2.0 installation instructions on the [wiki](https://github.com/jedisct1/dnscrypt-proxy/wiki/installation).
|
||||
|
||||
|
@ -33,7 +33,7 @@ Also see the [wiki](https://github.com/jedisct1/dnscrypt-proxy/wiki/DNS-server-s
|
|||
These instructions are the [same](https://github.com/pi-hole/pi-hole/wiki/DNSCrypt#change-your-dnsmasq-config), but will copy them here.
|
||||
|
||||
* `sudo nano /etc/dnsmasq.d/02-dnscrypt.conf`: Create new or edit existing conf.
|
||||
* Change `servers=<IP>#<port>` where `dnscrypt-proxy` is running. For example, my `.toml` file is `listen_addresses = ['127.0.0.1:54', '[::1]:54']`, so edit the conf file to be `server=127.0.0.1#54`
|
||||
* Change `server=<IP>#<port>` where `dnscrypt-proxy` is running. For example, my `.toml` file is `listen_addresses = ['127.0.0.1:54', '[::1]:54']`, so edit the conf file to be `server=127.0.0.1#54`
|
||||
* `sudo nano /etc/pihole/setupVars.conf`: Edit setupVars.conf.
|
||||
* Comment out `#PIHOLE_DNS#=` lines.
|
||||
* `sudo nano /etc/dnsmasq.d/01-pihole.conf`
|
||||
|
@ -45,7 +45,7 @@ These instructions are the [same](https://github.com/pi-hole/pi-hole/wiki/DNSCry
|
|||
Use the built-in client:
|
||||
|
||||
```sh
|
||||
dnscrypt-proxy -resolve google.com
|
||||
./dnscrypt-proxy -resolve google.com
|
||||
```
|
||||
|
||||
This will display the resolver you are currently using.
|
||||
|
|
Loading…
Add table
Reference in a new issue