Here are the results:
; <<>> DiG 9.16.48-Raspbian <<>> tricorder.pi-hole.net
;; global options: +cmd
;; connection timed out; no servers could be reached
Show the results of:
cat /etc/resolv.conf
Do you have a Wi-Fi connection via ethernet? I think pi-hole is only supported on 64-bit versions of raspberry pi os.
No.
Pi-hole can also be installed in 32-bit OS.
Eh... I had problems installing it on the 32 bit versions. might just by a glitch with my setup.
My pihole is just connected to the internet via wifi using its own wifi receiver.
@Gibbby87 Try:
nslookup tricorder.pi-hole.net
Post the whole response. Based on your last message, I'd expect it to say it can't find tricorder.pi-hole.net, but above that it will list what is configured to answer your DNS requests.
You need to connect it via ethernet you can get a micro usb to ethernet adapter that even has ports for a mouse and keyboard. Plus this can better configure it to block anything using your internet.
I'm not sure where your getting this from but wifi is perfectly fine. I've been using a pihole on wifi for a very long time. I can't remember the last time I had to do any setup / management on zerow / zerow2 / 3A + with anything but ssh. Raspberrypi imager allows you to config your wifi info into the image. As for speeds, you will have a small increase in latency using wifi over ethernet but its not enough to notice.
2 Likes
I've used this same pi hole on another network via wifi and it has worked just fine.
This is what returned:
;; connection timed out; no servers could be reached
You don't have any DNS, it doesn't look like. Probably need to start over and build a new OS image from scratch.
I was thinking of doing that and just to start from scratch.
I will redo the image tonight and report back tomorrow.
1 Like
'Gibbby87'
"I've used this same pi hole on another network via wifi and it has worked just fine."
Weird.
I have done a fresh install of the newest OS for pihole, but I am still in the same boat with all the suggested diagnoses in this thread so far.
The install went smoother this time around but I still can't upload a debug log and everything else that I said it couldn't do before. I am getting a new error now:
*Long-term load (15min avg) larger than number of processors: *1.1 > 1
This may slow down DNS resolution and can cause bottlenecks.
I'm beginning to wonder if my raspberry pi is malfunctioning.
Its possible. Did you do the install on a fresh SD card ?
I did, and I even used a new Micro SD card reader to eliminate that.
The install admittedly did do considerably better than the first time around, but I don't get the issues its having now. I know it has network access but its acting like it doesn't. As soon as I set the DNS on my router to go to the pihole it kicks my internet off. And as stated before I can't ping cloudflare but I can ping 1.1.1.1, so I am a bit confused.
When you say you're setting the DNS on your router to Pihole, elaborate on that. What kind of router? What specific DNS settings are you changing (WAN or LAN, for example)? What happens if you leave the router at its default and change one client (like a Windows PC, for example) to use Pihole?
Also, are you getting any warnings or errors in Pihole under Tools/Pi-hole Diagnosis?
More info as @nprampage mentioned would be good. Also can you post what your current ip -a is and the contents of cat /etc/resolv.conf ?