Resolver negleting extented unbound configuation file(s)

Software SW bugs discussion
1

Turris Omnia - rtrom01
Turris OS 3.9.6
Kernel 4.4.119-082ea0f4a4e204b99821bedcb349ed54-0
Unbound 1.6.8

sind uci does not support unbound forward-zone it requires an additional file /etc/unbound/unbound_ext.conf, which in this case reads

forward-zone:
  name: "."
  forward-addr: 9.9.9.9@853
  forward-tls-upstream: yes

restarted unbound with /etc/init.d/resolver restart, however the resulting unbound.conf is not showing the forward-zone. seems like the script is neglecting the /etc/unbound/unbound_ext.conf entirely.

If this is a bug than the same should be checked for /etc/unbound/unbound_srv.conf, which covers other server settings not supported through uci

2

Hi,
you can include custom config via unbound_includes section in /etc/config/resolver see https://gitlab.labs.nic.cz/turris/turris-os-packages/blob/test/net/resolver-conf/files/resolver-omnia-config#L62 .

Just for reference, related issue https://gitlab.labs.nic.cz/turris/turris-os-packages/issues/178

3

@paja thanks for the feedback and pointer.

Suppose if it was better doucmented this thread would not be necessary and saved time.

The below does not show in this installation (/etc/config/resolver) and would have saved effort/time it were there from the beginning

# config resolver 'unbound_includes'
# 	list include_path "/etc/unbound/unbound-part.conf"

include_path seems to be a bit misleading when it is pointing to a file really. Does it include only a specific file (in which case include_file would make more sense) or does it indeed include all files in a specified path, or even both?

Is there any documentation for resolver?