# Servers from the 'public-resolvers' source (see down below) can # Online documentation is available here:

# You should adjust it to your needs, and save it as 'dnscrypt-proxy.toml'

Make sure it works by querying your local DNS IP, e.g.:

In Advanced Settings, enable 'Use Conditional Forwarding', and enter the IP of the DHCP server (usually the router) as well as the domain (usually local for apple devices):.

Open the Pi-hole Admin Console (in your browser) and go to Settings > DNS.

This is useful to display device names instead if their IPs, when not using Pi-Hole as DHCP server.

Where it says: Enter one URL per line to add new blocklists Enter:.

Open the Pi-hole Admin Console (in your browser) and go to Settings > Blocklists.You can now enter your own DNS settings and click the 'Apply' button.Servers and relays may not be very stable.$ ( '#dhcp_dns_statistic' ). More information about ODoH protocol: Improving DNS Privacy with Oblivious DoH in 1.1.1.1Ĭaveats: The Oblivious DNS-over- HTTPS protocol is still a work in progress. # Configure 'ODoH servers' and 'ODoH relays' odoh_servers= '' odoh_relays= '' sed -i -e '32 s/.*/server_names = $odoh_servers/ 795 s/.*/routes = /' /etc /dnscrypt-proxy2 /*.toml # Enable ODoH on dnscrypt-proxy2 sed -i -e 's/.*odoh_servers.*/odoh_servers = true/ 689,700 s/#//' /etc /dnscrypt-proxy2 /*.toml You can change the ODoH servers and ODoH relays to any other. Relays can't get responses from a generic DoH server that doesn't support ODoH. Instead of directly sending a query to a target DoH server, the client encrypts it for that server, but sends it to a relay.Īn ODoH relay can only communicate with an ODoH server and an ODoH client. ODoH (Oblivious DNS-over-HTTPS) prevents servers from learning anything about client IP addresses, by using intermediate relays dedicated to forwarding encrypted DNS data.

Dnscrypt github