Resolv.conf entries parsing to which settings in the unbound daemon?

config resolver 'common'
	option forward_upstream '0'
	option keyfile '/etc/root.keys'
	option net_ipv6 '1'
	option net_ipv4 '1'
	option ignore_root_key '0'
	option static_domains '1'
	option dynamic_domains '1'

Having those settings it is not clear to me which settings in the master development are being matched and not withstanding not being mentioned in upstream either.
Thus how are they pertinent to unbound or just kresd?

I can’t say I know, but I believe all the implementation should be here: https://gitlab.labs.nic.cz/turris/turris-os-packages/blob/v3.11.2/net/unbound/files/unbound-init

1 Like

Thanks for the tip. :+1:

That explains almost all those entries except for dynamic_domains which does not have a definition. :slightly_frowning_face:

That’s the script that transfer information from DHCP to DNS: https://gitlab.labs.nic.cz/turris/turris-os-packages/blob/v3.11.2/net/resolver-conf/files/dhcp_host_domain_ng.py

1 Like

A bit of an eye opener really since it focuses on ipv4 and dnsmasq solely and neglecting odhcpd and ipv6 entirely

“DHCPv6 leases not supported now”