Hey there, today I updated my PiHole via pihole -up to the following versions:
- Core [v6.1.2]
- FTL [v6.2.3]
- Web interface [v6.2.1]
After this, everything went south. First off, I did all of this on screen because I'm not at home this week and next. In the middle of the updating process, it said it was waiting for DNS, but then it stopped with an error that the DNS is not doing its job. Sorry for the sloppy description; I tried to fix it as soon as possible because they have to work from Home here.
After this, i looked up the contents of /etc/resolve.conf and there was the following entry:
nameserver 192.168.0.10, which is the IP address of my Pi-hole Pi. I replaced it with nameserver 1.1.1.1 for testing purposes. Seeing domains are resolving now, I did pihole -r to repair the current installation.
That was successful, but somehow the DNS resolver still didn't work. After logging in to the Web Interface and trying to delete all current DHCP leases, I received the error message that DHCP wasn't activated, despite it being checked. I found this odd, so I deactivated DHCP, saved, then reactivated it, Saved Again, and the PI's load skyrocketed to 26, with all four cores reaching 100%.
Also, I got the error message that the database is locked.
I have noticed that the IP address range is set from 192.168.0.30 to 192.168.0.255, which isn't possible. That's what I have also seen in the Log files (range invalid). I now set it to 192.168.0.30 to 192.168.0.254. Right now, I have magically got it working somehow, but I can't figure out what happened.
I never changed anything in the last couple of updates. Is it even Possible to have /etc/resolv.conf pointing to Pi-hole?
As a sidenote, I have PIVPN GitHub - pivpn/pivpn: The Simplest VPN installer, designed for Raspberry Pi running on that Pi, too.
Can someone help me understand what happened here and how to fix the Problem Permanently? It also somehow managed to block all the connections from outside, like the connection to the cloud and game servers
If the Pi gets rebooted, the nameserver gets set back to ...0.10.
I hope I provided all the necessary information. If not, feel free to ask.
Expected Behaviour:
running its update and working
- Operating System (Family and Version)
PRETTY_NAME="Raspbian GNU/Linux 11 (bullseye)"
NAME="Raspbian GNU/Linux"
VERSION_ID="11"
VERSION="11 (bullseye)"
VERSION_CODENAME=bullseye
ID=raspbian
ID_LIKE=debian
Linux pihole 6.1.21-v7+ #1642 SMP Mon Apr 3 17:20:52 BST 2023 armv7l GNU/Linux
- Hardware
Raspberry Pi 3 Model B Rev 1.2
Actual Behaviour:
Bricked DNS and DHCP
Debug Token:
https://tricorder.pi-hole.net/OdiVniHj/
Thank you,
Daniel