Unbound + Wireguard Boot Error

[os914964619]

I just upgraded to 26.1.6 which required a reboot. When my opnsense router came back online, my Wireguard tunnel was not working. Looking at the logs:

2026-04-10T07:35:41-04:00Errorwireguard/usr/local/opnsense/scripts/wireguard/wg-service-control.php: The command </usr/bin/wg syncconf 'wg1' '/usr/local/etc/wireguard/wg1.conf'> returned exit code 1 and the output was "Name does not resolve: `mydomain.com:1234' Configuration parsing error"

Restarting the Wireguard service fixed this. I'm using Kea DHCP and I'm using Unbound for DNS but it appears that Wireguard was perhaps started before DNS could start. "Renew DNS for WireGuard on stale Connections" Cron does not fix this because the service never successfully started.

I'm not sure whether this regression was introduced in 26.1.6 or one of the last few versions that didn't require an OS reboot. I've never had this issue before on this router for the last few years until this recent OS reboot

[nero355]

Use the Forum Search with : Name does not resolve Configuration parsing error

And you will at least find two recent topics that I know of :
- https://forum.opnsense.org/index.php?topic=50748.msg259536;topicseen#msg259536
- https://forum.opnsense.org/index.php?topic=32232.msg256014;topicseen#msg256014

+ A lot more older topics mentioning this error.

Good luck! :)