The issue I am facing:
The Pi-hole doesn't seem to resolve anything for my devices that are using it for DNS. I first noticed this when the internet stopped working on my devices. I changed their DNS from the Pi-hole to Cloudflare and the internet started working immediately.
When I ssh'd in and ran pihole -up, I got this:
[✗] Retrieval of supported OS list failed. dig failed with return code 10.
Unable to determine if the detected OS (Raspbian 11) is supported
That lead me to this old thread which suggests running dig +short -t txt versions.pi-hole.net @ns1.pi-hole.net, which results in this:
dig: couldn't get address for 'ns1.pi-hole.net': failure
As a side note, when I run the same command on my local machine (while using Cloudflare for DNS), I get:
"Raspbian=9,10,11 Ubuntu=16,18,20,21 Debian=9,10,11 Fedora=33,34 CentOS=7,8"
...which makes me think it's not a router issue as suggested in that older post.
Other dig queries seem to also not work on the Pi-hole device (though I don't know if I'm reading this right):
john@raspberrypi:~ $ dig google.com
; <<>> DiG 9.16.22-Raspbian <<>> google.com
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 29121
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1472
;; QUESTION SECTION:
;google.com. IN A;; Query time: 40 msec
;; SERVER: 127.0.0.1#53(127.0.0.1)
;; WHEN: Sun Jan 02 17:48:19 PST 2022
;; MSG SIZE rcvd: 39
Here's one specifying Unbound:
john@raspberrypi:~ $ dig pi-hole.net @127.0.0.1 -p 5335
; <<>> DiG 9.16.22-Raspbian <<>> pi-hole.net @127.0.0.1 -p 5335
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 30937
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1472
;; QUESTION SECTION:
;pi-hole.net. IN A;; Query time: 40 msec
;; SERVER: 127.0.0.1#5335(127.0.0.1)
;; WHEN: Sun Jan 02 17:55:35 PST 2022
;; MSG SIZE rcvd: 40
Details about my system:
Using a Raspberry Pi Zero 2 W with this version of Raspian:
Distributor ID: Raspbian
Description: Raspbian GNU/Linux 11 (bullseye)
Release: 11
Codename: bullseye
Pi-hole versions:
Current Pi-hole version is v5.7
Current AdminLTE version is v5.9
Current FTL version is v5.12.1
I can't even post the tricoder link because of an error uploading the results:
- Error message: curl: (6) Could not resolve host: tricorder.pi-hole.net
However, here are a few errors from pihole -d:
*** [ DIAGNOSING ]: Name resolution (IPv4) using a random blocked domain and a known ad-serving domain
[✓] www.noknok.co is 0.0.0.0 on lo (127.0.0.1)
[✓] No IPv4 address available on wlan0
[✗] Failed to resolve doubleclick.com via a remote, public DNS server (8.8.8.8)
*** [ DIAGNOSING ]: Name resolution (IPv6) using a random blocked domain and a known ad-serving domain
[✓] u4803kjf03-955jkajfy5-n5892l56n-3576c5.netlify.app is :: on lo (::1)
[✓] u4803kjf03-955jkajfy5-n5892l56n-3576c5.netlify.app is :: on wlan0 ([redacted; not sure if this if private info])
[✓] u4803kjf03-955jkajfy5-n5892l56n-3576c5.netlify.app is :: on wlan0 ([redacted; not sure if this if private info])
[✗] Failed to resolve doubleclick.com via a remote, public DNS server ([redacted; not sure if this if private info])
*** [ DIAGNOSING ]: Dashboard and block page
[✗] Block page X-Header: X-Header does not match or could not be retrieved.
HTTP/1.1 200 OK
Content-type: text/html; charset=UTF-8
Expires: Mon, 03 Jan 2022 01:34:20 GMT
Cache-Control: max-age=0
Date: Mon, 03 Jan 2022 01:34:20 GMT
Server: lighttpd/1.4.59
What I have changed since installing Pi-hole:
I am using Unbound that was installed using this guide: unbound - Pi-hole documentation
I also have all logging disabled.