Project

General

Profile

Actions

Bug #4076

closed

DNS Forwarder options do not unset during CARP sync

Added by Jim Pingle almost 10 years ago. Updated over 5 years ago.

Status:
Resolved
Priority:
Normal
Category:
XMLRPC
Target version:
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 #1

Updated by Jim Thompson almost 10 years ago

  • Assignee set to Chris Buechler

assigned to Chris for evaluation.

Actions #2

Updated by Chris Buechler almost 10 years ago

  • Assignee changed from Chris Buechler to Renato Botelho

confirmed as described

Actions #3

Updated by Chris Buechler almost 10 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.

Actions #4

Updated by Renato Botelho almost 10 years ago

  • Status changed from Confirmed to Feedback
  • % Done changed from 0 to 100
Actions #6

Updated by Chris Buechler almost 10 years ago

  • Status changed from Feedback to Resolved

fixed

Actions #7

Updated by Jim Pingle over 5 years ago

  • Category changed from 62 to XMLRPC
Actions

Also available in: Atom PDF