DNS service not running after 3.3 update

[lastphoenix]

Hi Dan
admin portal its showing: DNS service not running

While in my case: net-tools is already the newest version.

sudo systemctl status dnsmasq gets:
● 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 Mon 2018-02-19 17:09:29 UTC; 47s ago
Process: 1969 ExecStartPre=/usr/sbin/dnsmasq --test (code=exited, status=1/FAILURE)

This happend while i upgraded from: Pi-hole Version v3.2.1 Web Interface Version v3.2.1 FTL Version vDev (master , v2.13.1)

to:Pi-hole Version v3.3 Web Interface Version v3.3 FTL Version v3.0

any suggestions?

best regards
Santo

[qwyrp]

I've the same issues as lastphoenix this was right after upgrading to:Pi-hole Version v3.3 Web Interface Version v3.3 FTL Version v3.0

[Mcat12]

Check the updates at the top of the blog post:
https://pi-hole.net/2018/02/14/pi-hole-v3-3-released-its-extra-special/

[lastphoenix]

thx. i did not see this post before. Now i got it (to work).

[lastphoenix]

Hi Mcat12
Well now pi-hole is runing and is blocking as i would ecptect it. thx for your documentation on how to get the lastest dnmasq.

But After one day in use, my "loca forward destination" droped from 52% to 36%. Also some ping test are indicating that caching is no longer working. Do you have observed this issue yet?

greetings
lastphoenix

[Mcat12]

We haven't seen this come up, but it is most likely just a variance in how the network is using Pi-hole that day, or since dnsmasq was restarted the cache had to be rebuilt and so more requests were forwarded.