Pi-hole/pi-hole
Pi-hole/pi-hole
1
0
Fork 0
mirror of https://github.com/pi-hole/pi-hole.git synced 2025-02-28 05:48:32 +00:00
Code Issues Projects Releases Packages Wiki Activity

Removed my changes, the setup I'd recommended was bypassing DNSCrypt and just relying on Pi-Hole to do all the work.

Error-418 2018-04-18 23:43:53 -07:00
parent b81fdd62c5
commit ed647600eb
1 changed files with 0 additions and 12 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

12
DNSCrypt-2.0.md

@ -40,18 +40,6 @@ These instructions are the [same](https://github.com/pi-hole/pi-hole/wiki/DNSCry
* Comment out `#server=...` lines * Comment out `#server=...` lines
* `sudo service dnsmasq restart`: restart dnsmasq * `sudo service dnsmasq restart`: restart dnsmasq
**NOTE** The changes to `/etc/pihole/setupVars.conf` and `/etc/dnsmasq.d/01-pihole.conf` may potentially block off DNSCrypt from reaching an external authoritative DNS server.
A workaround is to set one server in `setupVars.conf` and `01-pihole.conf` to use the IP address of an authoritative server on the net.
This was noted in one case on an AT&T U-verse connection when attempting to use Cloudflare's DNSCrypt service at 1.1.1.1.
For example (fixing Cloudflare's 4/1 service):
`PIHOLE_DNS1=1.0.0.1`
`server=1.0.0.1`
This allows Pi-Hole to bypass [AT&T's block on the 1.1.1.1 IP](https://blog.cloudflare.com/fixing-reachability-to-1-1-1-1-globally/) address and use Cloudflare's 4/1 service to properly authenticate requests.
## Test DNSCrypt ## Test DNSCrypt
Use the built-in client: Use the built-in client: