Bug #4076
closed
DNS Forwarder options do not unset during CARP sync
100%
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.
Updated by Jim Thompson over 9 years ago
- Assignee set to Chris Buechler
assigned to Chris for evaluation.
Updated by Chris Buechler over 9 years ago
- Assignee changed from Chris Buechler to Renato Botelho
confirmed as described
Updated by Chris Buechler over 9 years ago
though if you enable unbound, then dnsmasq is unset on the secondary. Doesn't happen just by disabling dnsmasq, that does sync the config across but doesn't update dnsmasq's config.
Updated by Renato Botelho over 9 years ago
- Status changed from Confirmed to Feedback
- % Done changed from 0 to 100
Applied in changeset f29fd4d08d910d6a10e294c555c052ae6a69c2b4.
Updated by Renato Botelho over 9 years ago
Applied in changeset 4469379c20d22b6c80bb7c47219e2fa2895c89a1.
Updated by