I had an old Pi3A running a repetier-server image, and decided to install pihole on it, which worked great... until the Pi seemed to be crashing after a few days.
So I upgraded to a Pi4, transfered the MicroSD and all seemed to be working, but for some reason I decided to do a fresh reinstall of the OS.
Since then, I can't get PiHole to resolve anything other than localhost queries.
Weirdly, straight after install I was getting DNS Service is NOT running, and a diagnosis about " cannot open or create lease file /var/lib/misc/dnsmasq.leases: Permission denied ".
fixes this, and everything is looking good on the admin page, except... on any devices in the house, all I get is:
nslookup pi.hole 192.168.1.241 - the pihole
DNS request timed out.
timeout was 2 seconds.
Server: UnKnown
Address: 192.168.1.241
DNS request timed out.
timeout was 2 seconds.
Only other thing I've done is change the webpage to port 81, as repetier server uses 80.
I've tried multiple repairs, reconfigure, fresh installs of the whole OS, and now trying an older pi image of repetier server, but I'm going round in circles doing the same thing over and over now.
You have some issues shown in your debug log - see excerpts below:
Pi-hole is configured for eth0, but this IP is not accepting DNS queries. There is an active wlan0 interface on a completely different LAN range, but Pi-hole isn't configured for this interface.
Check any firewall settings.
You have DNS 8.8.8.8 specified on the router in addition to Pi-hole's IP - don't do this.
*** [ DIAGNOSING ]: Name resolution (IPv4) using a random blocked domain and a known ad-serving domain
[✓] adserver-eu.adtech.advertising.com is 0.0.0.0 on lo (127.0.0.1)
[✗] Failed to resolve adserver-eu.adtech.advertising.com on eth0 (192.168.1.241)
[✓] adserver-eu.adtech.advertising.com is 0.0.0.0 on wlan0 (10.10.10.1)
[✓] doubleclick.com is 0.0.0.0 via a remote, public DNS server (8.8.8.8)
*** [ DIAGNOSING ]: Discovering active DHCP servers (takes 10 seconds)
Scanning all your interfaces for DHCP servers
Timeout: 10 seconds
* Received 304 bytes from eth0:192.168.1.1
Offered IP address: 192.168.1.241
Server IP address: 192.168.1.1
Relay-agent IP address: N/A
BOOTP server: (empty)
BOOTP file: (empty)
DHCP options:
Message type: DHCPOFFER (2)
server-identifier: 192.168.1.1
lease-time: 604800 ( 7d )
renewal-time: 302400 ( 3d 12h )
rebinding-time: 529200 ( 6d 3h )
netmask: 255.255.255.0
broadcast: 192.168.1.255
hostname: "Pi4"
wpad-server: "
"
dns-server: 192.168.1.241
dns-server: 8.8.8.8
router: 192.168.1.1
--- end of options ---
* Received 300 bytes from wlan0:10.10.10.1
Offered IP address: 10.10.10.27
Server IP address: 10.10.10.1
Relay-agent IP address: N/A
BOOTP server: (empty)
BOOTP file: (empty)
DHCP options:
Message type: DHCPOFFER (2)
server-identifier: 10.10.10.1
lease-time: 86400 ( 1d )
renewal-time: 43200 ( 12h )
rebinding-time: 75600 ( 21h )
netmask: 255.255.255.0
broadcast: 10.10.10.255
router: 10.10.10.1
dns-server: 10.10.10.1
--- end of options ---
DHCP packets received on interface wlan0: 1
DHCP packets received on interface eth0: 1
*** [ DIAGNOSING ]: Setup variables
PIHOLE_INTERFACE=eth0
PIHOLE_DNS_1=8.8.8.8
PIHOLE_DNS_2=8.8.4.4
I'm not sure what wlan is doing. On a previous install, I was struggling to disable it, and would get constant pihole errors to say it doesn't exist, but on this latest attempt, it has been disabled cleanly in OS, after pihole was installed. Either way, I'm definitely using eth0
2.ive had to configure 8.8.8.8 as secondary on the router, otherwise there is zero DNS resolution taking place on my network (couldn't even load Google to troubleshoot). Hoping to remove the entry once pihole starts working
Have you checked for firewalls on your network or Pi that block port 53 traffic? Pi-hole doesn't appear to be receiving port 53 traffic on the ethernet port.
From a network client, and from the terminal or command prompt on that client (and not via ssh to the Pi), what are the outputs of the following: