Router unresponsive after wan outtage

[Drftndak]

I tried searching for this on the forum and came up empty but that may be due to poor technical vocabulary. If it's been covered I apologize.

Yesterday I had my fiber line cut and as expected I kept humming along for about an hour on my self hosted services. But then all of a sudden I lost ability to connect to my router via the internal lan.

Bring up console via screen everything appears normal. I reboot the router now I can connect lan works fine. In roughly another hour or so again all clients and connections won't resolve to anything internal.

Is there some sort of timeout setting in unbound that im missing or somthing I may have misconfigured?

[cookiemonster]

something misconfigured or misunderstood.
p.s."But then all of a sudden I lost ability to connect to my router via the internal lan." It is unclear how. By ip address, by name (requires name resolution -DNS-)?.
For a bit of imagery, if there is a WAN interface and a LAN one on OPN, and a switch into that LAN port for LAN clients, then connecting by IP address amongst them is only through the switch, no OPN involved. For connecting by name, DNS internal is required and Unbound needs to be made to register records. If the WAN in down, all of this still works as it's all internal.