summaryrefslogtreecommitdiffstats
path: root/debian/NEWS
diff options
context:
space:
mode:
authorDaniel Baumann <daniel.baumann@progress-linux.org>2024-04-07 15:26:01 +0000
committerDaniel Baumann <daniel.baumann@progress-linux.org>2024-04-07 15:26:01 +0000
commitef03469fec14f1f0358b690934fc173d744f4e7d (patch)
tree8be439d7b2f1d7c8283b745919b9e66481a950e7 /debian/NEWS
parentAdding upstream version 5.6.0. (diff)
downloadknot-resolver-ef03469fec14f1f0358b690934fc173d744f4e7d.tar.xz
knot-resolver-ef03469fec14f1f0358b690934fc173d744f4e7d.zip
Adding debian version 5.6.0-1.debian/5.6.0-1debian
Signed-off-by: Daniel Baumann <daniel.baumann@progress-linux.org>
Diffstat (limited to '')
-rw-r--r--debian/NEWS40
1 files changed, 40 insertions, 0 deletions
diff --git a/debian/NEWS b/debian/NEWS
new file mode 100644
index 0000000..5df8f90
--- /dev/null
+++ b/debian/NEWS
@@ -0,0 +1,40 @@
+knot-resolver (5.1.2-1) unstable; urgency=medium
+
+ Up to Knot Resolver 4.x, network interface bindings and service
+ start were done by default via systemd sockets. These systemd sockets
+ are no longer supported, and upgrading from a 3.x version (as in Debian
+ Buster) requires manual action to (re)enable the service.
+
+ Please refer to kresd.systemd(7) and to the
+ /usr/share/doc/knot-resolver/upgrading.html file (from
+ knot-resolver-doc). An online version of the latter is available at
+ https://knot-resolver.readthedocs.io/en/stable/upgrading.html#x-to-5-x
+
+ For convenience, a suggested networking configuration can be found in
+ the file /var/lib/knot-resolver/.upgrade-4-to-5/kresd.conf.net
+
+ -- Santiago Ruano Rincón <santiago@debian.org> Tue, 28 Jul 2020 14:48:09 +0200
+
+knot-resolver (2.0.0-1) unstable; urgency=medium
+
+ Knot Resolver systemd service units are now templated, so that multiple
+ processes can run concurrently on multi-core systems. For a full
+ overview of the status of all the running daemons, use:
+
+ systemctl status system-kresd.slice
+
+ For more information about this setup, please see kresd.systemd(7).
+
+ -- Daniel Kahn Gillmor <dkg@fifthhorseman.net> Sat, 03 Feb 2018 22:51:02 -0500
+
+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 kresd.service` and
+ `systemd edit kresd.socket` to add more IP addresses, or just disable
+ it with `systemd mask kresd*.socket kresd.service` 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