Opnsense - How to Ensure Unbound is Restarted with Monit?

Hey All,

I was wondering if anyone has a full proof guide or have knowledge how to use MONIT within OPNSense to restart unbound after a failure.

I seem to have this issue here - Unbound crashing

It has been fairly persistant over the last couple of months and it’s really turning my once absolute rock solid router into a daily pain in the ass.
It seems to crash basically daily with

2023-12-19T03:20:01	Critical	unbound	[19574:9] fatal error: Could not initialize thread	
2023-12-19T03:20:01	Error	unbound	[19574:9] error: Could not set root or stub hints	
2023-12-19T03:20:01	Error	unbound	[19574:9] error: reading root hints /root.hints 60:33: Syntax error, could not parse the RR's class	
2023-12-17T10:50:01	Critical	unbound	[57385:7] fatal error: Could not initialize thread	
2023-12-17T10:50:01	Error	unbound	[57385:7] error: Could not set root or stub hints	
2023-12-17T10:50:01	Error	unbound	[57385:7] error: reading root hints /root.hints 2:15: Syntax error, could not parse the RR's type	
2023-12-16T02:01:16	Critical	unbound	[81602:1] fatal error: Could not initialize thread	
2023-12-16T02:01:16	Error	unbound	[81602:1] error: Could not set root or stub hints	
2023-12-16T02:01:16	Error	unbound	[81602:1] error: reading root hints /root.hints 2:13: Syntax error, could not parse the RR's type	
2023-12-15T17:23:13	Critical	unbound	[6243:8] fatal error: Could not initialize thread	
2023-12-15T17:23:13	Error	unbound	[6243:8] error: Could not set root or stub hints

I was hoping to be able to use MONIT to restart unbound?

I guess i could go another route and have HA monitor it and force a reboot if it see’s an internet issue.