# Require servers defined by remote sources to satisfy specific properties

# Use servers implementing the DNS-over-HTTPS protocol # Use servers implementing the DNSCrypt protocol # Use servers reachable over IPv6 - Do not enable if you don't have IPv6 connectivity # Require servers (from static + remote sources) to satisfy specific properties # Note (3): when using -pidfile, the PID file directory must be writable by the new user # Note (2): this feature is not compatible with systemd socket activation.

# Note (1): this feature is currently unsupported on Windows. # Switch to a different system user after listening sockets have been created. # Maximum number of simultaneous client connections to accept # List of local addresses and ports to listen to. # Remove the leading # first to enable this lines starting with # are ignored. # require_* filters will be used instead. # By default, this list is empty and all registered servers matching the

# Note that the require_* filters do NOT apply when using this setting. # The proxy will automatically pick working servers from this list. # 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.

Dnscrypt github