Hello,

one more question:

What is the proper way of autostarting Knot Resolver 1.4.0 on systemd (Debian Stretch in my case) to be able to listen on interfaces other from localhost?

As per the Debian README I've set up the socket override.

# systemctl edit kresd.socket:

[Socket]

ListenStream=<my.lan.ip>:53

ListenDatagram=<my.lan.ip>:53

   Loaded: loaded (/lib/systemd/system/kresd.socket; enabled; vendor preset: enabled)

  Drop-In: /etc/systemd/system/kresd.socket.d

           └─override.conf

   Active: failed (Result: resources)

     Docs: man:kresd(8)

   Listen: [::1]:53 (Stream)

           [::1]:53 (Datagram)

           127.0.0.1:53 (Stream)

           127.0.0.1:53 (Datagram)

           <my.lan.ip>:53 (Stream)

           <my.lan.ip>:53 (Datagram)

Oct 01 23:17:12 <myhostname> systemd[1]: kresd.socket: Failed to listen on sockets: Cannot assign requested address

Oct 01 23:17:12 <myhostname> systemd[1]: Failed to listen on Knot DNS Resolver network listeners.

Oct 01 23:17:12 <myhostname> systemd[1]: kresd.socket: Unit entered failed state.

To get it running I have to type in manually:

# systemctl start kresd.socket

I apologize, I am now to systemd and its socket activation so it's not clear to me whether service or socket or both have to be somehow set up to autostart or not.

Could anyone clarify this?

Oct 01 23:18:22 <myhostname> kresd[639]: [ ta ] keyfile '/usr/share/dns/root.key': not writeable, starting in unmanaged mode

The file has permissions 644 for root:root. Should this be owned by knot, or writeable by others?

Thanks!