-
Notifications
You must be signed in to change notification settings - Fork 976
Description
- This is not a support question, I have read about opensource and will send support questions to the IRC channel, GitHub Discussions or the mailing list.
- I have read and understood the 'out in the open' support policy
- I have read and understood the PowerDNS AI policy
- Program: Recursor
- Issue type: Bug report
Short description
New yaml-only config options are marked as Lua config, making pdns-rec impossible to start if any other Lua config is in use.
Environment
- Operating system: Debian 13
- Software version: 5.4.0-alpha1
- Software source: PowerDNS repository
Steps to reproduce
-
configure
recursor.lua_config_fileinrecursor.yml(using for instancerpzPrimaryis very useful for an environment without dynamically generated config files, ie a simple loop instead of a lot of repetitive config) -
configure
outgoing.tls_configurationsinrecursor.yml
Expected behaviour
Pdns-rec should run as there is no conflicting config (tls_configurations does not actually have any Lua counterpart)
Actual behaviour
Pdns-rec refuses to start. Error message:
YAML settings include values originally in Lua but also sets `recursor.lua_config_file`. This is unsupported
Other information
New yaml-only configuration options are flagged as Lua options, effectively making any use of Lua config impossible as pdns-rec cannot start if there is conflicting use of yaml/Lua config:
alldefault = alldefault && settings.outgoing.tls_configurations.empty(); // actually not a Lua item, but very much alike
alldefault = alldefault && settings.logging.opentelemetry_trace_conditions.empty(); // actually not a Lua item, but very much alike
https://github.com/PowerDNS/pdns/blob/rec-5.4.0-alpha1/pdns/recursordist/rec-rust-lib/cxxsupport.cc#L1432-L1433
https://github.com/PowerDNS/pdns/blob/rec-5.4.0-alpha1/pdns/recursordist/rec-rust-lib/cxxsupport.cc#L1457-L1458