Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
DNSMasq fails after update to Pihole 4 #2379
In raising this issue, I confirm the following:
How familiar are you with the the source code relevant to this issue?:
a working upgrade
DNSMasq failure, result in no internet at all.
Steps to reproduce:
In putty i used the command
In browser, i visit my pihole admin page and noticed the following error in the left top corner https://i.imgur.com/gmA4ol7.png
I tried the command
The log also confirms it is an DNSMasq issue "dnsmasq deamon is failed" https://i.imgur.com/e0axd8W.png
This all happened after
Previous version worked flawless.
Debug token provided by uploading
Troubleshooting undertaken, and/or other relevant information:
@DL6ER Well the pihole upgrade just messed all up. See screenshots the DNSMasq deamon is failed. It has to do with the upgrade. No more internet after the pihole v4 upgrade. I disabled Pihole in my router now otherwise i wouldn't even be online right now.
So... in Pihole V4 in the admin panel it shows the DNS error in the left corner on top, so there IS a DNS issue due to Pihole v4 upgrade.
@DL6ER Maybe in future version better communicate things like a message in the upgrade process that can't be ignored. Like a warning that pihole doesn't use DNSMasq anymore or other things have been removed. Because right now i am already busy with this issue for 6 hours, ended up removing pihole from my router untill i have a solution.
@jacobsalmela wrote this in his blog post (https://pi-hole.net/2018/08/06/pi-hole-v4-0-released-with-ftldns-improved-blocking-modes-regex-docker-and-more/#more-19078) but I agree that we could have been even more explicit about this.
Reverting to a previous version is only supported with docker images if I'm not mistaken (I have never tried this myself).
and chose to repair your installation. This will temporarily chose 18.104.22.168 as your upstream provider (but only for downloading the most recent version of pihole-FTL). This change should automatically be reverted by
@DL6ER that worked, thanks.
What does echo "22.214.171.124" | sudo tee /etc/resolv.conf mean?
Okay, glad to see that you already found the answer to your question already.
I overlooked this at first, but on a second look to your linked screenshot, I saw the
and assumed that name resolution didn't work on your system and hence the downloading of the core component
Do you have any further issues now or is everything resolved?
ok, sorry to roll this up but i have exactly this problem with my pihole that i use for my phone.
In my case tho its slightly different. I use ym raspi as a eth0-wlan0 bridge, means i use my pihole already on the br0 interface to just get onto my raspi
Now i wanted to update again after a while from 3.1 to 4.0, so i did my apt-get update and upgrade, then the pihole -up command, and saw the github problem and later the DNS resolution problem. SSH still worked, my bridge did too, but my raspi could not get again into the itnernet. i tried to reconfigure it to make sure its still working on the right interface etc but no change there. I did the repair, no change, i found the Dnsmasq error on version 3.3 and used that, updated it to 2.6 as stated on another site with a fix, still nothing was working
Then i saw this here, tried it, but i couldnt get anything at all, not with 126.96.36.199, not with 188.8.131.52 not with 184.108.40.206, so im slightly at a miss ehre why its not working.
and yes, the rest is exactly as stated above by nomoreads, just that i have a wifi-bridge installed too