Pihole device cannot access internet, but blocking is working

Expected Behaviour:

Trying to run my discord bot on the pihole alongside pihole itself. (or rather, i've had the discord bot on it for years, pihole is new as of today) and the raspberry pi (zero W) is unable to access the internet itself. I thought it was just an issue with my bot, but as it turns out pihole is unable to download blocklists from github as well.

Actual Behaviour:

Pi-hole is working, ads are being blocked, router is using pihole as dns, all things are well outside the pihole. The pihole device itself is completely unable to access the internet. Like it's blocking its own dns.

I have read no less than 40 similar articles, but edint etc/resolv.conf and restarting the dns doesn't help. restarting the device didn't help. Restarting the router didn't help.

Setting the local dns (on pihole device) to 8.8.8.8 or 1.1.1.1, or (local router dns) or (isp dns server) all do not help. I'm at a complete lose here.

Debug Token:

-paste deleted and link removed for apparent security concerns, mods request a dm or propose some other way to post the log if necessary-

1. [i] Default IPv4 gateway(s):

2. [i] Default IPv6 gateway(s):

No gateways defined?

The mods ask you to upload your default log to their site so that people like me cannot read your log, only them, as a security measure.

I mean, i'm no expert, but if it's all local network stuff, i don't see much of an issue with it, but duly noted, i guess. Either way, i cannot give them a token because my device is unable to upload the log and generate the token.

In which case... what am i to do instead?

Ahh, sorry, due to my poor vision i failed to see your gateway suggestion, where do I edit this at?
I do not see this in the dhcpd file.
I've got moderate experience with linux commandline (hosting a discord bot and managing minecraft server nodes for a few years)
but my knowledge for it was extremely laser focused on exactly what I needed to perform those tasks, this is entirely new to me, and only some of it makes sense.

I do not understand why your pihole diagnosis does not show a default gateway but you say pihole is working so there must be a default gateway. Type route on the command line. On the same line as default it should have your routers IP address. Hopefully someone who knows will come along shortly.

ryuhouji@microhost:~ $ route
Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
192.168.0.0     0.0.0.0         255.255.255.0   U     302    0        0 wlan0

doesn't look correct


but, the pihole is definitely working, so idk

I checked my dhcpd.conf, just to make sure, and it has my correct router address


static_routers=192.168.0.1 is my router/gateway address, and it should be working.

I found my own solution messing around. All i had to do was add a manual route with

sudo route add default gw 192.168.0.1

Thanks, Moto for leading me in the right direction!

This topic was automatically closed 21 days after the last reply. New replies are no longer allowed.