Can't seem to get pi-hole working with dnscrypt

[Billagee]

Please follow the below template, it will help us to help you!

Expected Behaviour:

[Replace this text with what you think should be happening]
Expecting all dns queries on my network to route to the pi-hole which is connected via ethernet to my router which is dhcp server

Actual Behaviour:

[replace this text with what is actually happening]
Not receiving queries

Debug Token:

https://tricorder.pi-hole.net/u6fpf7uc7x

[DanSchaper]

You have 3 upstream DNS servers listed in your configuration, so those are the servers that will get the queries:

*** [ DIAGNOSING ]: Setup variables
    PIHOLE_DNS_3=127.0.0.1#54
    PIHOLE_DNS_1=208.67.222.222
    PIHOLE_DNS_2=208.67.220.220

It looks like queries to the IP address of the Pi-hole are failing:

*** [ DIAGNOSING ]: Name resolution (IPv4) using a random blocked domain and a known ad-serving domain
[✓] static.novanet.vn is 0.0.0.0 via localhost (127.0.0.1)
[✗] Failed to resolve static.novanet.vn via Pi-hole (192.168.1.107)
[✓] doubleclick.com is 216.58.200.14 via a remote, public DNS server (8.8.8.8)

And there appears to be only one client using the Pi-hole DNS. (127.0.0.1)

   [2020-02-24 13:19:42.217 1023] Imported 197 queries from the long-term database
   [2020-02-24 13:19:42.217 1023]  -> Total DNS queries: 197
   [2020-02-24 13:19:42.217 1023]  -> Cached DNS queries: 137
   [2020-02-24 13:19:42.217 1023]  -> Forwarded DNS queries: 59
   [2020-02-24 13:19:42.217 1023]  -> Exactly blocked DNS queries: 1
   [2020-02-24 13:19:42.217 1023]  -> Unknown DNS queries: 0
   [2020-02-24 13:19:42.217 1023]  -> Unique domains: 25
   [2020-02-24 13:19:42.217 1023]  -> Unique clients: 1
   [2020-02-24 13:19:42.217 1023]  -> Known forward destinations: 2

*** [ DIAGNOSING ]: Pi-hole log
-rw-r--r-- 1 pihole pihole 39346 Feb 24 13:25 /var/log/pihole.log
   -----head of pihole.log------
   Feb 24 01:00:00 dnsmasq[990]: query[PTR] 1.1.168.192.in-addr.arpa from 127.0.0.1
   Feb 24 01:00:00 dnsmasq[990]: config 192.168.1.1 is NXDOMAIN
   Feb 24 01:00:00 dnsmasq[990]: query[PTR] 2.0.6.10.in-addr.arpa from 127.0.0.1
   Feb 24 01:00:00 dnsmasq[990]: config 10.6.0.2 is NXDOMAIN
   Feb 24 01:00:00 dnsmasq[990]: query[PTR] 220.220.67.208.in-addr.arpa from 127.0.0.1
   Feb 24 01:00:00 dnsmasq[990]: forwarded 220.220.67.208.in-addr.arpa to 127.0.0.1
   Feb 24 01:00:00 dnsmasq[990]: forwarded 220.220.67.208.in-addr.arpa to 208.67.220.220
   Feb 24 01:00:00 dnsmasq[990]: forwarded 220.220.67.208.in-addr.arpa to 208.67.222.222
   Feb 24 01:00:01 dnsmasq[990]: reply 208.67.220.220 is resolver2.opendns.com
   Feb 24 01:00:01 dnsmasq[990]: query[PTR] 222.222.67.208.in-addr.arpa from 127.0.0.1
   Feb 24 01:00:01 dnsmasq[990]: cached 208.67.222.222 is resolver1.opendns.com
   Feb 24 02:00:00 dnsmasq[990]: query[PTR] 1.1.168.192.in-addr.arpa from 127.0.0.1
   Feb 24 02:00:00 dnsmasq[990]: config 192.168.1.1 is NXDOMAIN
   Feb 24 02:00:00 dnsmasq[990]: query[PTR] 2.0.6.10.in-addr.arpa from 127.0.0.1
   Feb 24 02:00:00 dnsmasq[990]: config 10.6.0.2 is NXDOMAIN
   Feb 24 02:00:00 dnsmasq[990]: query[PTR] 220.220.67.208.in-addr.arpa from 127.0.0.1
   Feb 24 02:00:00 dnsmasq[990]: cached 208.67.220.220 is resolver2.opendns.com
   Feb 24 02:00:00 dnsmasq[990]: query[PTR] 222.222.67.208.in-addr.arpa from 127.0.0.1
   Feb 24 02:00:00 dnsmasq[990]: cached 208.67.222.222 is resolver1.opendns.com
   Feb 24 03:00:00 dnsmasq[990]: query[PTR] 1.1.168.192.in-addr.arpa from 127.0.0.1

What upstream should be used and what IP address are you setting on the clients?

[Billagee]

Hi, let me tinker around a bit more and revert! Thanks very much