It seems that Unbound DNS is losing its binding to a CARP VIP after failover/failback, because it does not automatically re-attach to the VIP when it returns. I need to manually restart Unbound to refresh its interface/IP bindings, restoring full DNS service on the VIP.
This behavior is a seems to be a common issue with Unbound in CARP HA environments. When the CARP VIP fails back to the original master, Unbound DNS sometimes needs to be restarted because it does not dynamically re-bind to the VIP after it returns to the interface.
Is there a way to force a an unbound restart when failover to backup or failback to master even occurs?
D
Do you have Unbound listening on "All (recommended)"?
I found that reco and implemented it today. Will post with results after I test it for a few cycles.
Thanks for the heads up.
D
This seems to be working fine. I am updating subject to solved.