pfSense

When updating static DHCP leases the call to services_unbound_configure on the services_dhcp page causes a full rebuild of the unbound configure and a restart. This causes host resolution to fail while unbound is offline which in my environment takes 20+ seconds. DNS shouldn't be down for that long - especially when adding a static entry. Even with CARP setup both unbound services go down at near the same time.

This was corrected in my environment by changing the kill - config - start procedure of the services_unbound_configure() in services.inc to getting rid of the kill and calling unbound_control("reload") instead of sync_unbound_service().

Both adds and deletes work fine from services_dhcp and the reload now happens in less then 1 second with no perceivable loss of service.

Perhaps a modification of the unbound restart/reload functions would allow us to avoid the kill and rebuild kitchen sync call of unbound to be where it's not necessary.