Unbound Stops Resolving DNS Queries due to DHCP registrations

Describe the bug

Unbound Stops Resolving DNS Queries due to DHCP registrations

I recently created a new box and imported a configuration from another box.
After the migration, the new box was causing intermittent outages
Digging around I realized IP networking worked but DNS queries were failing to get resolved.
The box is setup as Primary using CARP and the Secondary box has no issues with synced configurations.
After troubleshooting and isolating the issue to the new box with the imported configurations, the one difference is that I introduced swap into the system. The underlying HW is virtualized previously with VMWare and now with Proxmox.
The secondary box was migrated to Proxmox as a whole system and has not had the same intermittent DNS issues as the primary.
After disabling DHCP registrations in Unbound, the primary has been running stable for 7 hours. Normally DNS queries fail after 4 hours.

Troubleshooting Steps

I tried to reload all the services from the cli, but the process would stop and be stuck after openssh server. I noticed that the next service that was undergoing a reload was unbound.
From there I tried to reload the service from the Web Interface and I tried to stop it from the web interface. Neither action would work. Sometimes the web gui would be stuck loading.
There is definitely something wrong with the unbound service installed on the primary because if I go to stats after DNS goes down on the network, the entire web gui would freeze and be unresponsive.

Solution Used

I found this link and discovered this issues exists with pfsense + unbound. https://forum.netgate.com/topic/153913/solved-unbound-stops-resolving-intermittently/8
First I forced Carp to failover to the secondary so I can get the DNS queries to work and keep the network running
- ( Interfaces > Virtual IPs > Status > Enter Persistent Carp Maintenance)
I had to lookup the Unbound Process and give it the kill -KILL <unbound PID> because HUP or any other signal would not work.
Go to Services > Unbound > General to disable the DHCP registrations and Static mappings option,
From there, start the Unbound DNS service from the web gui
Leave Persistent Carp Maintenance
All the DNS queries worked again, web gui freezes stopped and all other issues I've experienced with Unbound since importing the primary's configuration to a newly installed box have stopped.

Background on the Primary and Secondary

This outage only occurs on the Primary box.
This box used a new install of OPNsense and then I loaded a backup configuration to it.
The new box has swapped enabled when the old one did not.
The configuration came from a box that was upgraded to the latest version of OPNsense last month.
- This was an upgrade from the previous version of OPNsense on the original box that was hosted as a VM on esxi.
The secondary box was an esxi image that I later imported into proxmox.
This import involved migrating the entire disk image from esxi to proxmox, so all data is the same (mac addresses stayed the same but I changed the nic drivers to virtio just as I did with the primary).
The big difference is that the secondary was upgraded to the latest OPNsense version and continues to be the same machine.

opnsense / core