knot-resolver (1.1.0~git2016072900-1) unstable; urgency=medium

  * Knot Resolver now starts and runs under unprivileged user and uses a
    socket activations to bind on the privileged ports.  That means that if
    you use anything more complicated than that you need to either override
    the default service file with `systemd edit knot-resolver.service`, or
    just disable it and provide your own custom system service file tailored
    to your needs.

 -- Ondřej Surý <ondrej@debian.org>  Thu, 04 Aug 2016 09:04:53 +0200
