summaryrefslogtreecommitdiffstats
path: root/doc/man_knotd.rst
blob: d0fe83bcb37cfb63ce078cb88788afb57f63c446 (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
.. highlight:: none

``knotd`` – Knot DNS server daemon
==================================

Synopsis
--------

:program:`knotd` [*config_option*] [*options*]

Description
-----------

Knot DNS is a high-performance authoritative DNS server. The `knotd` program is
the DNS server daemon.

Config options
..............

**-c**, **--config** *file*
  Use a textual configuration file (default is :file:`@config_dir@/knot.conf`).

**-C**, **--confdb** *directory*
  Use a binary configuration database directory (default is :file:`@storage_dir@/confdb`).
  The default configuration database, if exists, has a preference to the default
  configuration file.

Options
.......

**-m**, **--max-conf-size** *MiB*
  Set maximum size of the configuration database
  (default is @conf_mapsize@ MiB, maximum 10000 MiB).

**-s**, **--socket** *path*
  Use a remote control UNIX socket path (default is :file:`@run_dir@/knot.sock`).

**-d**, **--daemonize** [*directory*]
  Run the server as a daemon. New root directory may be specified
  (default is :file:`/`).

**-v**, **--verbose**
  Enable debug output.

**-h**, **--help**
  Print the program help.

**-V**, **--version**
  Print the program version.

Signals
.......

If the `knotd` process receives a SIGHUP signal, it reloads its configuration and
reopens the log files, if they are configured. When `knotd` receives a SIGUSR1
signal, it reloads all configured zones. Upon receiving a SIGINT signal, `knotd`
exits.

Exit values
-----------

Exit status of 0 means successful operation. Any other exit status indicates
an error.

See Also
--------

:manpage:`knot.conf(5)`, :manpage:`knotc(8)`, :manpage:`keymgr(8)`,
:manpage:`kjournalprint(8)`.