Well, then. Something is wrong with our config. Let me check. In the meantime, can you verify if you can ping google.com and/or 8.8.8.8 from your Pi-hole device?
PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data.
64 bytes from 8.8.8.8: icmp_seq=1 ttl=59 time=18.1 ms
64 bytes from 8.8.8.8: icmp_seq=2 ttl=59 time=16.9 ms
64 bytes from 8.8.8.8: icmp_seq=3 ttl=59 time=15.2 ms
64 bytes from 8.8.8.8: icmp_seq=4 ttl=59 time=15.6 ms
ping: unknown host google.com
now that's interesting...
What's in /etc/resolv.conf and systemctl status dnsmasq?
systemctl status dnsmasq
● dnsmasq.service - dnsmasq - A lightweight DHCP and caching DNS server
Loaded: loaded (/lib/systemd/system/dnsmasq.service; enabled)
Drop-In: /run/systemd/generator/dnsmasq.service.d
└─50-dnsmasq-$named.conf, 50-insserv.conf-$named.conf
Active: failed (Result: exit-code) since Sa 2018-02-17 23:48:34 CET; 22min ago
Process: 449 ExecStartPre=/usr/sbin/dnsmasq --test (code=exited, status=1/FAILURE)
/etc/resolv.conf
[details="Summary"]
# Generated by dhcpcd from eth0
# /etc/resolv.conf.head can replace this line
nameserver 127.0.0.1
# /etc/resolv.conf.tail can replace this line
[/details]
just for the fun of it: Changed the nameserver to the routers IP and am testing pihole -r now
It will likely work then. What's dnsmasq -v and what version of Raspbian are you running?
dnsmasq -v
Dnsmasq Version 2.72
cat /etc/os-release
PRETTY_NAME="Raspbian GNU/Linux 8 (jessie)"
NAME="Raspbian GNU/Linux"
VERSION_ID="8"
VERSION="8 (jessie)"
ID=raspbian
ID_LIKE=debian
HOME_URL="http://www.raspbian.org/"
SUPPORT_URL="http://www.raspbian.org/RaspbianForums"
BUG_REPORT_URL="http://www.raspbian.org/RaspbianBugs"
uname -a
Linux n3tb0x 4.9.78+ #1084 Thu Jan 25 17:40:10 GMT 2018 armv6l GNU/Linux
I managed to run pihole -d the token is: xm5ovq1tnm
dnsmasq still not running.
Ahh yep. The version of dnsmasq in Jessie doesn't support the --extra flag in this release. We're working on a fix. You can revert to the previous version of Pi-hole for now. Not the most glamorous, but we're also looking at getting a later version of dnsmasq installed but it's still in the works.
2 Likes
This fixed the issue.
Thank you so very much, for the quick and high quality, late night, replies! :-)
There's only one question left: How can I get back to current branch, after reverting to the previous version?
Just in case I am going wild and upgrade raspbian to stretch in the near future.
/tldr: sudo nano /etc/resolv.conf (change the nameserver to your router's IP) and then apply the fix as described here.
You can replace the versions in those commands with master, and you will be on the latest versions.
1 Like
I have the same question; my issue was exactly the same as described above. Pihole just wouldn't work and my Pi was not resolving DNS queries. I reverted to the 3.21 Version a described above (very slick Jacob) and it now works, but I have two questions now:
- How do I know when the dnsmasq issue is resolved
2, How do I get the Pihole system back to where it is current and checking for updates?
Please keep in mind I am a complete noob when it comes to this. COMPLETE. Please take a look at the attached screenshot from the Web UI. I hate to admit it, but I am one of those folks that need the step by step. Thank you all for your help!
We've come up with a way for users on Jessie to use the required version of dnsmasq. This will also fix the version issues you see and will let you easily update:
https://pi-hole.net/2018/02/14/pi-hole-v3-3-released-its-extra-special/
1 Like
Awesome, thank you. That seems simple enough, but I did downgrade to the previous version so my pihole would work. How do I revert it back so I can update?
pihole checkout master might do the trick. Run that after updating dnsmasq though.
Excellent -following your instructions did the trick EXACTLY for me. Bravo, sir (or ma'am). I am now updated and on latest version!
This may be a bit off-topic, but I; a gonna ask: Is there any reason for us on Jessie to upgrade to latest OS? Are there any real enhancements for us running pihole? That would require a complete wipe and update, right, for there is no way to upgrade an OS image other than install?
I only ask because of the problem we had in this thread. Thank you, Developers!!!
Here's some information on updating to Stretch (a reflash is not necessarily required): Raspbian Stretch has arrived for Raspberry Pi - Raspberry Pi
Unless there's a reason to stay on Jessie, you should update to Stretch.
Dont' know about enhancements other than the better logging via the new dnsmasq version.
I did the update (jessie -> stretch) yesterday without wiping the os.
There are a few sites that describe easy approaches to update to the newest version without wiping, including the official raspberrypi.org.
However I'd strongly advise to backup your current system before doing the upgrade as there's always a chance for distribution upgrades to crash and leave the system unusable.
For all changes that come with stretch please refer to the official Debian notes.
Edit: Sorry Mcat12 was faster than me.
1 Like
This topic was automatically closed 21 days after the last reply. New replies are no longer allowed.