Bug 13991

Summary: Knot-resolver does not start when /var/run/dns1 does not exist
Product: IPFire Reporter: Stefan Schantl <stefan.schantl>
Component: ---Assignee: Assigned to nobody - feel free to grab it and work on it <nobody>
Status: CLOSED FIXED QA Contact:
Severity: - Unknown -    
Priority: - Unknown - CC: adolf.belka, michael.tremer
Version: 2   
Hardware: unspecified   
OS: Unspecified   
Bug Depends on:    
Bug Blocks: 13972    

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.
Comment 6 Michael Tremer 2026-07-20 16:14:18 UTC 
Core Update 203 has been released:

> https://www.ipfire.org/blog/ipfire-2-29-core-update-203-released