I installed Pi-hole two days ago, and I am still evaluating if it is functioning correctly, as the logs are not being generated in the way that I think they should based on tutorials. I am using a router w/ OpenWRT and edited the default DNS under interfaces ->
There are several errors shown in your debug log that indicate the Pi-Hole is not connected to your network properly:
There is no IP address assigned to the Pi-Hole on the ethernet gateway where Pi-Hole is listening:
*** [ DIAGNOSING ]: Networking
[✗] No IPv4 address(es) found on the eth0 interface.
[✗] No IPv6 address(es) found on the eth0 interface.
[i] Default IPv4 gateway: 192.168.1.1
* Pinging 192.168.1.1...
[✗] Gateway did not respond. (https://discourse.pi-hole.net/t/why-is-a-default-gateway-important-for-pi-hole/3546)
Pi-Hole is not resolving queries using the IP address it is configured for (192.168.1.128). Note that it can resolve using itself, so it's set up properly on the Pi. The problem is the Pi connecting to your network.
*** [ DIAGNOSING ]: Name resolution (IPv4) using a random blocked domain and a known ad-serving domain
[✓] pisosribarroja.es is 0.0.0.0 via localhost (127.0.0.1)
[✗] Failed to resolve pisosribarroja.es via Pi-hole (192.168.1.128)
*** [ DIAGNOSING ]: Setup variables
PIHOLE_INTERFACE=eth0
IPV4_ADDRESS=192.168.1.128/24
If you have DHCP enabled on your router (and from your first debug log it appears you do), you don't need to enable this on the Pi-Hole. This gets two DHCP servers running which typically causes problems on a network. Turn off DHCP on your Pi-Hole.
You set up the interface for whichever way you are connecting the Pi to your internet (ethernet or wireless). Is your Pi connected via ethernet or via wireless to your network?
Your new debug token shows the same problem - no IPv4 address on eth0, the interface on which Pi-Hole is listening.
fixed, wlan0 is now set. Looks like the one issue is ipv6 not resolving for a DNS request and dnsmasq not active - should I activate dnsmasq as well? If so what would be the best way for this?
With Pi-Hole V4, dnsmasq is embedded in pihole-FTL and pihole-FTL runs in place of dnsmasq. The debug log will typically show dnsmasq as "failed" or "inactive." You should not activate dnsmasq as a separate process.
ok thanks, I'm testing it by going on adladen websites that are recommended for testing pihole. After going on this site for example there are no new hits in the admin panel I Don't Like Being A Mother and the page still displays ads interspersed in the text. I also am able to still go on a domain that I added into the blacklist w/ the REGEX * (^|.)domain.com$
That could be a case of your router or client providing an alternate DNS (i.e. not Pi-Hole) that the client is using to get those domains. If you recently set this up, you may have to renew your client DHCP leases to pick up the new DNS information.
Some routers have DNS settings buried in various menus and it sometimes takes a bit of digging to find them all.
thanks - restarted router, I am seeing the other devices in Top Clients and the data on the admin panel is updating, but ads are still visible on pages like this https://pythontips.com/tag/python-patreon/
