The short story is "DNS service is NOT running". It reports this status on the web interface and via pihole status check. Despite this it seems to still be properly blocking and logging everything I've asked it to. Blacklisted sites are blocked also.
This is a fresh Hyper-V of Ubuntu 17.04 - dual processors w/ 2gb dedicated ram to the VM
Pi-Hole 3.0.1
Web ver 3.0.1
FTL ver 2.6.2
Debug token sn35ncirya
The long version of this story started yesterday when I did an update from ver 2.x.x to 3.0.1. I noticed it was responding sluggishly and for the life of me could NOT get FTL to start or run. After unsuccessfully testing the various fixes for FTL issues I gave up and started fresh. Wiped and created a new VM then did a clean install of 3.0.1. That fixed FTL.
(side note.... FTL isn't working on a different machine I updated from 2.x to 3.0.1 either)
Now this new issue popped up with the DNS service reporting off but actually seems to be on., I do not get an error if I start it manually but is just returns a status of not running if I check it again. If I start it via web page it will go green then go back to not running status if I refresh the page.
Anyone seen this issue pop up? Did the same thing when I tried to set it up on a Debian image also.
-SOLVED-
I looked in the logs after doing a pihole -d and saw an error reference to line 238. Turned out the netstat command was not installed. Installed it any it is showing the DNS service running properly. Now I just gotta figure out the FTL issue on the other box.
HI There,
I am having the same issue, just installed Pi-hole on spare laptop with UBUNTU.
Running the latest version of UBUNTU and PI-hole. My status is the same, the DNS service is not running.
Seems to block ads for a while and then it stops.
I just started this so if anybody can help, I'd appreciate it. Any info required, please let me know.
Thanks,
Hi Dan,
Thanks very much for your reply. I managed to fix it and the DNS service is running now. I did not realize that the gentleman that posted the initial issue included the fix there. Took me a while to figure it out but I did it I am just getting my feet wet with pi-hole so...
I hadn't had a chance to reply so...
Now though, I have the following problems., when I try to update the domain lists, I get status 000. Please take a look at the output below:
::: Neutrino emissions detected...
:::
::: Pulling source lists into range... done!
:::
::: Getting raw.githubusercontent.com list... done
::: Status: Status 000
::: List download failed, using cached list (list not updated!)
::: Getting mirror1.malwaredomains.com list... done
::: Status: Status 000
::: List download failed, using cached list (list not updated!)
::: Getting sysctl.org list... done
::: Status: Status 000
::: List download failed, using cached list (list not updated!)
::: Getting zeustracker.abuse.ch list... done
::: Status: Status 000
::: List download failed, using cached list (list not updated!)
::: Getting s3.amazonaws.com list... done
::: Status: Status 000
::: List download failed, using cached list (list not updated!)
::: Getting s3.amazonaws.com list... done
::: Status: Status 000
::: List download failed, using cached list (list not updated!)
::: Getting hosts-file.net list... done
::: Status: Status 000
::: List download failed, using cached list (list not updated!)
:::
::: Aggregating list of domains... done!
::: Formatting list of domains to remove comments.... done!
::: 128651 domains being pulled in by gravity...
::: Removing duplicate domains.... done!
::: 105011 unique domains trapped in the event horizon.
:::
::: Adding adlist sources to the whitelist... done!
::: Whitelisting 6 domains... done!
::: Nothing to blacklist!
::: No wildcards used!
::: Formatting domains into a HOSTS file... done!
:::
::: Cleaning up un-needed files... done!
:::
::: Refresh lists in dnsmasq... done!
::: DNS service is running
::: Pi-hole blocking is Enabled
:::
::: Neutrino emissions detected...
:::
::: Pulling source lists into range... done!
:::
::: Getting raw.githubusercontent.com list... done
::: Status: Status 000
::: List download failed, using cached list (list not updated!)
::: Getting mirror1.malwaredomains.com list... done
::: Status: Status 000
::: List download failed, using cached list (list not updated!)
::: Getting sysctl.org list... done
::: Status: Status 000
::: List download failed, using cached list (list not updated!)
::: Getting zeustracker.abuse.ch list... done
::: Status: Status 000
::: List download failed, using cached list (list not updated!)
::: Getting s3.amazonaws.com list... done
::: Status: Status 000
::: List download failed, using cached list (list not updated!)
::: Getting s3.amazonaws.com list... done
::: Status: Status 000
::: List download failed, using cached list (list not updated!)
::: Getting hosts-file.net list... done
::: Status: Status 000
::: List download failed, using cached list (list not updated!)
:::
::: Aggregating list of domains... done!
::: Formatting list of domains to remove comments.... done!
::: 128651 domains being pulled in by gravity...
::: Removing duplicate domains.... done!
::: 105011 unique domains trapped in the event horizon.
:::
::: Adding adlist sources to the whitelist... done!
::: Whitelisting 6 domains... done!
::: Nothing to blacklist!
::: No wildcards used!
::: Formatting domains into a HOSTS file... done!
:::
::: Cleaning up un-needed files... done!
:::
::: Refresh lists in dnsmasq... done!
::: DNS service is running
::: Pi-hole blocking is Enabled
When I run pihole -up, I get errors about unable to connect to https://git... The command does find updates but cannot install them.
Do you still want the debug token?
Apologies for sounding dumb, as I said I am new to Linux/pi-hole.
I was experiencing the same "DNS Service not running" issue. After some forensics and back tracking, I found that it started occurring around the time I'd put some iptables rules in place. I found that pihole requires TCP:53 access to localhost.
Adding "-A INPUT -s 127.0.0.0/8 -p tcp -m tcp --dport 53 -j ACCEPT" to my rule set fixed the issue.
I am just getting my feet wet with pi-hole so...