Wireguard - if no dns is available at service start, tunnel doesnt come up until wireguard service restart

[Bash-Ninja]

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/plugins/blob/master/CONTRIBUTING.md
• I have searched the existing issues, open and closed, and I'm convinced that mine is new.
• The title contains the plugin to which this issue belongs

Describe the bug
If Internet / DNS is available after the wireguard service startet a connection to a wireguard peer which contains a dns name and not an ip doesnt come up. Only a wireguard service restart then leads to a successful connection.

To Reproduce
Steps to reproduce the behavior:

1. Setup Wireguard where the remote peer is setup using a dns name
2. Break DNS Resolving / Internet
3. Reboot Opnsense
4. Wait
5. Enable DNS Resolving / Internet again
6. Wireguard Tunnel is not up because the service couldnt resolve the remote peer DNS Name to an ip

Expected behavior
Tunnel comes up as soon as DNS Resolving works again

Additional context
It appears to be some kind of stale state in which wireguard says "oh i couldnt resolve the hostname" but doesnt recheck like every minute or so...