Bug #4067
closed
Unbound configuration does not get synchronized to the secondary members of a cluster install
Added by Ermal Luçi over 11 years ago.
Updated over 6 years ago.
Description
Unbound configuration does not get synchronized to the secondary members of a cluster install.
There is no provisioning today for this on the synchronizationcode.
- Category changed from DNS Forwarder to 62
- Status changed from New to Confirmed
probably should add a new config sync checkbox for DNS Resolver, and leave DNS Forwarder as is.
- Assignee set to Ermal Luçi
Ermal reported it, I'm assigning it to him. :-)
- Assignee changed from Ermal Luçi to Renato Botelho
- Status changed from Confirmed to Feedback
- % Done changed from 0 to 100
Applied in changeset commit:c25caf5b01269961d0129f8f83dc8dc1a078c3a8.
Applied in changeset commit:73041230a79f7b0f2cbae60cf51596a1232d5029.
- Status changed from Feedback to Resolved
- Category changed from 62 to XMLRPC
Also available in: Atom
PDF