Unbound: Require manual restart to populate system AAAA record

[ovv]

Important notices

Before you add a new report, we ask you kindly to acknowledge the following:

• I have read the contributing guide lines at https://github.com/opnsense/core/blob/master/CONTRIBUTING.md
• I am convinced that my issue is new after having checked both open and closed issues at https://github.com/opnsense/core/issues?q=is%3Aissue

Describe the bug

The system AAAA record is not present when starting unbound.

To Reproduce

Steps to reproduce the behavior:

1. Start opnsense
2. Query the system record:
   dig opnsense.example.com A @opnsense.example.com -> correct response
   dig opnsense.example.com AAAA @opnsense.example.com -> NXDOMAIN
3. Restart unbound from the web UI
4. Query the system record:
   dig opnsense.example.com A @opnsense.example.com -> correct response
   dig opnsense.example.com AAAA @opnsense.example.com -> correct response

Expected behavior

No need to restart unbound manually to get the system AAAA record created

Describe alternatives you considered

For static IP someone could use Unbound host overrides

Screenshots

Unbound configuration

Relevant log files

If applicable, information from log files supporting your claim.

Additional context

The IPv6 WAN address is obtained using DHCP over the IPv4 connectivity

My guess is that unbound is started once the IPv4 is assigned and no IPv6 is present, then when the IPv6 is obtained unbound doesn't restart/reload

Environment

OPNsense 24.7.7-amd64
FreeBSD 14.1-RELEASE-p5
OpenSSL 3.0.15