Dnsmasq to old!

Help Synology
1

Hi,

I've installed Pi-hole on a DS216+II and made it work besides one little issue. It seems dnsmasq is to old because it doesn't recognize the option "log-queries=extra". If I try to enable logging I get the following:
root@feedme:/var/log# pihole logging on
[i] Enabling logging...
[✗] Restarting DNS forwarder and DHCP server: configuration syntax check failed!
[✓] Logging has been enabled!

The pihole.log looks like this:
root@feedme:/var/log# more pihole.log
May 19 09:43:35 dnsmasq[12057]: exiting on receipt of SIGTERM
May 19 09:43:37 dnsmasq[13135]: started, version 2.72 cachesize 10000
May 19 09:43:37 dnsmasq[13135]: compile time options: IPv6 GNU-getopt DBus i18n IDN DHCP DHCPv6 no-Lu
a TFTP conntrack ipset auth DNSSEC loop-detect
May 19 09:43:37 dnsmasq[13135]: using nameserver 8.8.4.4#53
May 19 09:43:37 dnsmasq[13135]: using nameserver 8.8.8.8#53
May 19 09:43:37 dnsmasq[13135]: read /etc/hosts - 4 addresses
May 19 09:43:37 dnsmasq[13135]: read /etc/pihole/local.list - 2 addresses
May 19 09:43:37 dnsmasq[13135]: failed to load names from /etc/pihole/black.list: No such file or dir
ectory
May 19 09:43:38 dnsmasq[13135]: read /etc/pihole/gravity.list - 122093 addresses

I've tried apt-get update and apt-get upgrade but there's nothing outdated.

How do I fix this?

Edit:
Ok, I found this thread: Pi-hole working but no statistics which describes the very same problem. So I "just" have to figure out, how to manually upgrade dnsmasq.

Dirk

2

Yup, you can upgrade dnsmasq or revert to an older version of Pi-hole.

3

Or maybe another dns daemon is already active ?

dehakkelaar@nas:~$ sudo netstat -nltup | grep ':53 '
tcp        0      0 172.17.0.1:53           0.0.0.0:*               LISTEN      23716/named
tcp        0      0 169.254.91.208:53       0.0.0.0:*               LISTEN      23716/named
tcp        0      0 169.254.101.54:53       0.0.0.0:*               LISTEN      23716/named
tcp        0      0 169.254.151.137:53      0.0.0.0:*               LISTEN      23716/named
tcp        0      0 10.0.0.3:53             0.0.0.0:*               LISTEN      23716/named
tcp        0      0 127.0.0.1:53            0.0.0.0:*               LISTEN      23716/named
tcp6       0      0 :::53                   :::*                    LISTEN      23716/named
udp        0      0 172.17.0.1:53           0.0.0.0:*                           23716/named
udp        0      0 169.254.91.208:53       0.0.0.0:*                           23716/named
udp        0      0 169.254.101.54:53       0.0.0.0:*                           23716/named
udp        0      0 169.254.151.137:53      0.0.0.0:*                           23716/named
udp        0      0 10.0.0.3:53             0.0.0.0:*                           23716/named
udp        0      0 127.0.0.1:53            0.0.0.0:*                           23716/named
udp6       0      0 :::53                   :::*                                23716/named
4

Yeah, thanks. Found that one too. :slight_smile:

5

The port isn't blocked. DNS is working fine. Just no logging and therefore no statistics.