This is a Raspberry PI 4 running the octoprint image (so octoprint is running on its ports), it is also running home bridge, as well as pi-hole... all of this over WLAN. The only non-standard thing I've done is change lighttpd to listen on a custom port for the web interface (which is totally reachable).
Pi-hole was working fine over night, and around noon today it just stopped working. I am able to access all the UIs over the local network by visiting pi.hole, or octopi.local etc... but when ssh'd into the pi, I can't resole URLs.
For instance:
ON THE PIE:
; <<>> DiG 9.11.5-P4-5.1-Raspbian <<>> @127.0.0.1 google.com
; (1 server found)
;; global options: +cmd
;; connection timed out; no servers could be reached
I can traceroute 1.1.1.1... and it takes a while, but gets there eventually...
Having some trouble uploading the debug log (as the pi has no external dns resolution)... I'm happy to work with anyone here if they have advice.
Trying to upload a debug log again by substituting 9.9.9.9 for 127.0.0.1 in /etc/resolve.conf doesn't appear to be working either.
The above might be a bit stream of consciousness'y, sorry!
Gave that a shot (second to last paragraph) Anything I should do to force that change to take effect?
pi@octopi:~ $ cat /etc/resolv.conf
# Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
# DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
nameserver 9.9.9.9
[?] Would you like to upload the log? [y/N] y
* Using curl for transmission.
[✗] There was an error uploading your debug log.
* Please try again or contact the Pi-hole team for assistance.
* A local copy of the debug log can be found at: /var/log/pihole_debug.log
If it's any help, my router is an Eero. I haven't set up the router to forward DHCP to the pi-hole, instead setting each device to speak directly to the pie-hole for now.