is potential privacy/security issue, with kresd each user can have resolver cache
in their private directory and use it in similar fashion to keychain.
-By default, no configuration is needed, only a directory where the daemon can store
-runtime data (cache, control sockets, ...)
.P
To use a locally running
.B kresd
.IR resolv.conf (5)
and start
.B kresd
-.PP
-.nf
-.RS 6n
-$ kresd -a 127.0.0.1
-[system] interactive mode
->
-.RE
-.fi
-.PP
-.P
-The daemon may be configured also as a plain forwarder using query policies, that requires
-creating a file
-.B config
-in daemon runtime directory. See \fIdaemon/README.md\fR for more information about interacting
-with CLI and configuration file options, or visit
-.B https://knot-resolver.readthedocs.io
-online documentation.
-.PP
-.nf
-.RS 6n
-# Create a basic forwarder configuration
-$ cat << EOF > config
-modules = { 'policy' }
-policy.add(policy.all(policy.FORWARD('192.168.1.1')))
-$ kresd -a 127.0.0.1
-EOF
-.RE
-.fi
-.PP
+
.P
+The daemon may be configured also as a plain forwarder using query policies.
+This requires using a config file. Please refer to documentation for
+configuration file options. It is available at
+\fIhttps://knot-resolver.readthedocs.io\fR or in package documentation
+(available as knot-resolver-doc package in most distributions).
+
The available CLI options are:
.TP
.B \-a\fI addr[@port]\fR, \fB\-\-addr=\fI<addr[@port]>
.TP
.B \-c\fI config\fR, \fB\-\-config=\fI<config>
Set the config file with settings for kresd to read instead of reading the
-file at the default location (\fIconfig\fR). The syntax is
-described in \fIdaemon/README.md\fR.
+file at the default location (\fIconfig\fR).
.TP
.B \-f\fI N\fR, \fB\-\-forks=\fI<N>
This option is deprecated since 5.0.0!