I know there are a few here who are much more knowledgable about things like pi-hole, and I need help to solve a problem without going too far down a rabbit hole. I do have other things (TEA) I would rather be doing.
I noticed some strange things happening this week, including the return of ads. Pi-hole takes care of that, right?
Not when it is being bypassed.
I discovered my ISP had reset the modem/router unit in my home back to defaults.
As a result, the router was doing DHCP and the ISP was providing DNS. This is absolutely NOT what I wanted and was changed without my permission
.
So I spent the morning fettling around with things and thought I had fixed it.
DHCP is once again turned OFF on the router, just the way it was when I set it up.
The Primary DNS once again points to my Pi-hole.
However, in my previous setup, the secondary DNS pointed to 0.0.0.0.
This time, I had to point the secondary DNS to my Pi-hole as well, in order for the router to accept the change in settings.
After that, I was happy. I could return to browsing eevblog.com
and things like google (sans ads) worked.
However, SWMBO was the first to discover that all is not well in the world.
It turns out quite a number of things do not work, while others do. For example, Yahoo and Keysight could not be accessed.
The Query Log in Pi-hole is giving me some clues.
For the sites that are not working, the Status is Unknown(0), whereas sites that are working have a status OK(...)
Does anyone have any experience with this sort of thing? It almost looks like there is something wrong with a DNS cache or an upstream DNS server.
Of course, I am starting to get out of my league at this point.
Google is a bit of a useless tease since I can get search results, but mostly cannot access the website that returned in the search result!
Any ideas?
![Scared :scared:](https://www.eevblog.com/forum/Smileys/default/scared.gif)
Try this:
first, upgrade your pi-hole:
- login to the pihole with ssh
example from mine (it has the IP 192.168.1.111 yours is very likely different):
ssh -l pi 192.168.1.111
- then become root
sudo su -
- then execute these commands in this order
apt-get update
apt-get -y upgrade
/usr/local/bin/pihole -up
init 6; exit
it is a good idea to reboot a machine after running an upgrade.
- once the pi-hole is up and running again, create a cronjob, so the pi-hole will do every 24h an update and a reboot
- execute these instructions in this order
- login to the pi-hole and become root as described above
- create a config file for the crontab
echo "* 2 * * * /root/pihole.sh" >> /root/crontab.2020062901
- create a cronjob. * 2 * * * means: run this job at 2am every 24h
crontab /root/crontab.2020062901
- check, if the cronjob is in place:
crontab -l
- create a little shellscript with the name pihole.sh. The easiest to do so is copy&paste the lines between the ******
******* begin script *******
echo "#!/bin/bash
apt-get update
apt-get -y upgrade
apt-get -y dist-upgrade
apt-get -y auto-remove
/usr/local/bin/pihole -up
init 6; exit" > pihole.sh
******* end script ********
- change the attributes of pihole.sh so it will become executable
chmod 750 /root/pihole.sh
Hope that helps.