Output of the following commands:
./dnscrypt-proxy -version
2.0.45
./dnscrypt-proxy -check
[2021-06-11 07:44:10] [NOTICE] dnscrypt-proxy 2.0.45
[2021-06-11 07:44:10] [NOTICE] Source [public-resolvers] loaded
[2021-06-11 07:44:10] [NOTICE] Source [relays] loaded
[2021-06-11 07:44:11] [NOTICE] Configuration successfully checked
./dnscrypt-proxy -resolve example.com
Resolving [example.com] using 127.0.0.1 port 54
Resolver : 74.63.20.246 (res101.qpg.rrdns.pch.net.)
Lying : no
DNSSEC : yes, the resolver supports DNSSEC
Canonical name: example.com.
IPv4 addresses: 93.184.216.34
IPv6 addresses: 2606:2800:220:1:248:1893:25c8:1946
Name servers : b.iana-servers.net., a.iana-servers.net.
DNSSEC signed : yes
Mail servers : 1 mail servers found
HTTPS alias : -
HTTPS info : -
Host info : -
TXT records : v=spf1 -all, 8j5nfqld20zpcyr8xjw0ydcfq9rk8hgm
What is affected by this bug?
- I have Pi-hole installed on a Raspberry pi 4B. I am using a Custom upstream DNS (127.0.0.1#54). (Note: This is the only DNS Pi-hole send queries to for resolution)
- At port 54 of the Pi, is where I have dnscrypt-proxy listening at, with
server_names = ['quad9-doh-ip4-filter-pri']
- dnsleaktest shows that I resolve via WoodyNet (as expected for quad9), Cloudflare (why?)
When does this occur?
Everytime! Flushed DNS, still occurs.
Where does it happen?
How do we replicate the issue?
Expected behavior (i.e. solution)
No cloudflare DNS;-;
Other Comments
Output of the following commands:
./dnscrypt-proxy -version
2.0.45./dnscrypt-proxy -check
./dnscrypt-proxy -resolve example.com
What is affected by this bug?
server_names = ['quad9-doh-ip4-filter-pri']When does this occur?
Everytime! Flushed DNS, still occurs.
Where does it happen?
How do we replicate the issue?
Expected behavior (i.e. solution)
No cloudflare DNS;-;
Other Comments