Package: avahi-daemon
Version: 0.6.32-1
Severity: normal
Dear Mai N'tainer,
* What led up to the situation?
Booting or recovering from RAM sleep lead to name resolution breakdown.
dnscrypt-proxy use port 5353 and bind point to it as the only forwarder.
avahi-daemon has been installed as other packages dependency
and left as is; I do not use it.
* What exactly did you do (or not do) that was effective (or
ineffective)?
At first, I thought it was a dnscrypt-proxy problem until I run:
netstat -pan|grep 53|grep -v unix
that show port 5353 belong to avahi-daemon:
avahi-daemon ON:
================
tcp 0 0 127.0.0.1:953 0.0.0.0:* LISTEN
8488/named
tcp 0 0 127.0.0.1:5353 0.0.0.0:* LISTEN
1/init
tcp 0 0 192.168.1.233:53 0.0.0.0:* LISTEN
8488/named
tcp 0 0 127.0.0.1:53 0.0.0.0:* LISTEN
8488/named
tcp6 0 0 :::53 :::* LISTEN
8488/named
udp 0 0 192.168.1.233:53 0.0.0.0:*
8488/named
udp 0 0 127.0.0.1:53 0.0.0.0:*
8488/named
udp 0 0 192.168.1.233:41176 192.168.1.1:5351 ESTABLISHED
2998/dring
udp 0 0 0.0.0.0:5353 0.0.0.0:*
10061/avahi-daemon:
udp 0 0 127.0.0.1:5353 0.0.0.0:*
1/init
udp6 0 0 :::53 :::*
8488/named
udp6 0 0 :::5353 :::*
10061/avahi-daemon:
avahi-daemon OFF:
=================
tcp 0 0 127.0.0.1:953 0.0.0.0:* LISTEN
8488/named
tcp 0 0 127.0.0.1:5353 0.0.0.0:* LISTEN
1/init
tcp 0 0 192.168.1.233:53 0.0.0.0:* LISTEN
8488/named
tcp 0 0 127.0.0.1:53 0.0.0.0:* LISTEN
8488/named
tcp6 0 0 :::53 :::* LISTEN
8488/named
udp 0 0 192.168.1.233:53 0.0.0.0:*
8488/named
udp 0 0 127.0.0.1:53 0.0.0.0:*
8488/named
udp 0 0 192.168.1.233:41176 192.168.1.1:5351 ESTABLISHED
2998/dring
udp 0 0 127.0.0.1:5353 0.0.0.0:*
1/init
udp6 0 0 :::53 :::*
8488/named
(Quite a strange thing that dnscrypt-proxy appears as the init process,
guess it is, once again, a magnificent feature of shitstemd that knows
much better than any admin how to do things on his own machine, even
against his will…)
* What was the outcome of this action?
Stopping avahi-daemon made my day.
Note that if I play a bit with it, after 2-3 stop/start/restart I'm obliged to
kill -9 it (seven times before it dies, guess because of shitstemd.)
* What outcome did you expect instead?
avahi-daemon not covering dnscrypt-proxy port.
Have a nice day.
-- System Information:
Debian Release: stretch/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 4.7.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=fr_FR.utf8, LC_CTYPE=fr_FR.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages avahi-daemon depends on:
ii adduser 3.115
ii bind9-host [host] 1:9.10.3.dfsg.P4-10.1
ii dbus 1.10.12-1
ii host 1:9.10.3.dfsg.P4-10.1
ii init-system-helpers 1.45
ii libavahi-common3 0.6.32-1
ii libavahi-core7 0.6.32-1
ii libc6 2.24-5
ii libcap2 1:2.25-1
ii libdaemon0 0.14-6
ii libdbus-1-3 1.10.12-1
ii libexpat1 2.2.0-1
ii lsb-base 9.20161016
Versions of packages avahi-daemon recommends:
ii libnss-mdns 0.10-7
Versions of packages avahi-daemon suggests:
pn avahi-autoipd <none>
-- Configuration Files:
/etc/resolvconf/update-libc.d/avahi-daemon [Errno 2] No such file or directory:
u'/etc/resolvconf/update-libc.d/avahi-daemon'
-- no debconf information
