1. DNS/KnotResolver/config

Knot Resolver daemon https://knot-resolver.readthedocs.io/en/v3.2.1/daemon.html

https://knot-resolver.readthedocs.io/en/latest/

https://knot-resolver.readthedocs.io/en/latest/quickstart-config.html

https://knot-resolver.readthedocs.io/en/latest/quickstart-config.html#scenario-internal-resolver

https://knot-resolver.readthedocs.io/en/latest/quickstart-config.html#scenario-personal-resolver

DNSSEC, data verification

/DNSSEC /mode https://knot-resolver.readthedocs.io/en/latest/config-dnssec.html#mode

confはどこに置くものか。

Configuration syntax

The configuration is kept in the config file in the daemon working directory,
and it’s going to get loaded automatically.

If there isn’t one, the daemon is going to start with sane defaults, listening on localhost. 

modules = {
        predict = {
                window = 15, -- 15 minutes sampling window
                period = 6*(60/15) -- track last 6 hours
        }
}

This module requires ‘stats’ module to be present and loaded.

Use period 0 to turn off prediction and just do prefetching of expiring records.

2. Running supervised

$ python scripts/supervisor.py ./daemon/kresd -a 127.0.0.1

3. configuratian

http://knot-resolver.readthedocs.io/en/latest/daemon.html#configuration

In it’s simplest form it requires just a working directory in which it can set up persistent files like cache and the process state.

If you don’t provide the working directory by parameter,

• it is going to make itself comfortable in the current working directory.