If you're using our packages with systemd with sockets support (not supported
on CentOS 7), network interfaces are configured using systemd drop-in files.
-Each protocol has its own configuration file:
+
+Each protocol has its own configuration file. *By default, these are configured
+to listen on localhost.*
.. csv-table::
:header: "**Network protocol**", "**Socket file name**"
":ref:`mod-http-doh`","``kresd-doh.socket``"
":ref:`Web management <mod-http-built-in-services>`","``kresd-webmgmt.socket``"
-To configure kresd to listen on a public interface using the original DNS protocol,
+.. warning:: You MUST NOT repeat the localhost defaults in the following
+ drop-in overrides, otherwise the socket will fail to start with "Address in
+ use" error. To view the entire socket configuration, including any drop-ins,
+ use systemctl cat.
+
+To configure kresd to listen on a **public interface** using the original DNS protocol,
create a drop-in file:
.. code-block:: bash
This manual page describes how to manage \fBkresd\fR using \fBsystemd\fR
units.
-.B Socket activation
+.B QUICKSTART
+
+.nf
+.RS 4n
+\fBsystemctl start kresd@1\fR - single instance of kresd, responding on localhost
+.RE
+.fi
+
+.B SOCKET ACTIVATION
\fBkresd\fR integration with systemd takes advantage of socket activation,
which enables the daemon to run without super user priviledges or any
.RE
.fi
-.B Configuring network interfaces
+.B CONFIGURING NETWORK INTERFACES
+
+By default, \fBkresd is configured to listen on localhost\fR (see ports above).
+You MUST NOT repeat these defaults in the following drop-in overrides,
+otherwise the socket will fail to start with "Address in use" error. To view
+the entire socket configuration, including any drop-ins, use \fBsystemctl
+cat\fR.
-To configure \fBkresd\fR to listen on public interfaces, drop-in files (see
+To configure \fBkresd\fR to listen on \fBpublic interfaces\fR, drop-in files (see
\fIsystemd.unit\fR(5)) should be used. These can be created with:
.nf
For more detailed socket configuration, see \fBsystemd.socket\fR(5).
-.B Concurrent daemons
+.B CONCURRENT DAEMONS
\fBkresd\fR daemon can be executed in multiple independent processes, which are
managed with \fBsystemd\fR via systemd templates (see \fBsystemd.unit\fR(5)).