Bug 13991 - Knot-resolver does not start when /var/run/dns1 does not exist
Summary: Knot-resolver does not start when /var/run/dns1 does not exist
Status: MODIFIED
Alias: None
Product: IPFire
Classification: Unclassified
Component: --- (show other bugs)
Version: 2
Hardware: unspecified Unspecified
: - Unknown - - Unknown -
Assignee: Assigned to nobody - feel free to grab it and work on it
QA Contact:
URL:
Keywords:
Depends on:
Blocks: KRESD
  Show dependency tree / graph
 
Reported: 2026-05-27 06:52 UTC by Stefan Schantl
Modified: 2026-05-27 10:53 UTC (History)
1 user (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Stefan Schantl 2026-05-27 06:52:36 UTC 
I've configured a C203 VM to use red as static and the knot-resolver does not get up properly during boot up.

When I try to manually start the resolver got the following error message:

 08:46:16 	kresd[4177]: 	[system] error while loading config: /usr/lib/knot-resolver/config.lua:165: bad argument #1 to 'lines' (/var/run/dns1: No such file or directory) (workdir '/run/knot-resolver')
Comment 1 Stefan Schantl 2026-05-27 06:54:31 UTC 
PS:

The same error also happens when "/var/run/dns2" does not exist.
Comment 2 Stefan Schantl 2026-05-27 06:55:40 UTC 
PPS:

After manually creating both files (empty), knot-resolver started successfully.
Comment 3 Stefan Schantl 2026-05-27 07:02:45 UTC 
After checking the DNS settings file, I found, that the USE_ISP_NAMESERVERS vaule is enabled (default value on new installations).

In conclusion with this setting the config.lua script requires the "/var/run/dns*/ files to obtain the assigned DNS servers, which never happens on a static confgured RED interface.