Actions
Bug #4076
closedDNS Forwarder options do not unset during CARP sync
Start date:
12/04/2014
Due date:
% Done:
100%
Estimated time:
Plus Target Version:
Release Notes:
Affected Version:
All
Affected Architecture:
All
Description
With a CARP cluster, the options on Services > DNS Forwarder will sync to the secondary when set, but when unset they do not get removed from the secondary.
This includes the Enable box, DHCP lease boxes, Query forwarding options, even Strict Interface Bindings, listen port, etc.
If you check a box or enter a value it will sync that to the secondary but when unchecking/removing values they do not replicate.
This is not a regression as the same issue is present on 2.1.x. With users needing to disable the DNS Forwarder to migrate to Unbound it may become more of a problem.
Actions