Show Posts
1
23.7 Legacy Series / Unbound not starting after reboot
« on: September 28, 2023, 12:02:54 pm »
If you configure Network Interfaces in Unbound DNS/General to use specific Interfaces and if you are using IPv6, Unbound DNS does not start...
When trying unbound -c /var/unbound/unbound.conf it appears that unbound can't bind (a) IP adress(es)...
The issue is the same as I described it under https://forum.opnsense.org/index.php?topic=33815.msg176314#msg176314. Due to the IPv6 configuration and (correct) protocol behavior and a - as I see it meanwhile bug in the current Interface, the Webconfigurator does, replicable, add a dynamic IPv6 address per interface to the configuration.
If, at reboot for example, the dynamic IPv6 changes (which is in default IPv6 configurations very likely and according to the protocol, wished / accepted), the configuration doesn't... unfortunate that the IP is then not existing on the specified interface and therefore the service can't bind it...
The issue does not appear if you leave Network Interfaces to reply on all interfaces. And again, the drop-down behavior is buggy, it does save 'changes' as described in the linked forum entry above
Temporarily work-around:
* fix the configuration file
* don't open the Webconfiguration Page of Unbound DNS
When trying unbound -c /var/unbound/unbound.conf it appears that unbound can't bind (a) IP adress(es)...
The issue is the same as I described it under https://forum.opnsense.org/index.php?topic=33815.msg176314#msg176314. Due to the IPv6 configuration and (correct) protocol behavior and a - as I see it meanwhile bug in the current Interface, the Webconfigurator does, replicable, add a dynamic IPv6 address per interface to the configuration.
If, at reboot for example, the dynamic IPv6 changes (which is in default IPv6 configurations very likely and according to the protocol, wished / accepted), the configuration doesn't... unfortunate that the IP is then not existing on the specified interface and therefore the service can't bind it...
The issue does not appear if you leave Network Interfaces to reply on all interfaces. And again, the drop-down behavior is buggy, it does save 'changes' as described in the linked forum entry above
Temporarily work-around:
* fix the configuration file
* don't open the Webconfiguration Page of Unbound DNS