===================
You can use HTTP API to dynamically change configuration of already running Knot Resolver.
-By default the API is configured as UNIX domain socket ``manager.sock`` located in the resolver's rundir (typically ``/run/knot-resolver/``).
+By default the API is configured as UNIX domain socket located in the resolver's rundir ``/var/run/knot-resolver/manager.sock``.
This socket is used by ``kresctl`` utility in default.
The API setting can be changed only in ``/etc/knot-resolver/config.yaml`` configuration file:
:option:`--socket <-s <socket>, --socket <socket>>` option to tell
``kresctl`` where to look for the API.
-If the ``management`` key is not present in the configuration file, ``kresctl``
-attempts to connect to the ``/var/run/knot-resolver/manager.sock`` Unix-domain
-socket, which is the Manager's default communication channel.
+If the :ref:`management <manager-api>` key is not present in the configuration file,
+``kresctl`` attempts to connect to the ``/var/run/knot-resolver/manager.sock``
+Unix-domain socket, which is the Manager's default communication channel.
By default, ``kresctl`` tries to find the correct communication channel in
``/etc/knot-resolver/config.yaml``, or, if present, the file specified by the