Bug #5441
closed
Unbound config does not bind to CARP IP
Added by Jeremy Porter almost 9 years ago.
Updated over 8 years ago.
Description
After upgrading a working 2.2.5 system, there was no name resolution on the LAN. Lan is set to query the Carp VIP for DNS. Changing Unbound config to add the CARP interface IP as an assigned interface does not work. It does not appear to update the unbound.conf file to include the IP. Temporary workaround is to bind Unbound to all interfaces.
- Assignee set to Renato Botelho
- Status changed from New to Confirmed
Unbound seems to have lost all knowledge of CARP IPs, they no longer show up in the interfaces list.
- Status changed from Confirmed to Feedback
Maybe it was fixed by recent changes, I couldn't reproduce. On my tests I can see CARP IPs available on 'Network Interfaces' list
I can retest, but this only happened on upgrade
- Status changed from Feedback to Assigned
Nevermind, I'll test it on upgrade then
- Assignee changed from Renato Botelho to Luiz Souza
Probably another side-effect of #4858
- Status changed from Assigned to Feedback
- % Done changed from 0 to 100
This is one of the issues already fixed in #4858 (similar to #5464).
- Status changed from Feedback to Assigned
- Status changed from Assigned to Resolved
- Assignee changed from Luiz Souza to Chris Buechler
this was fixed by my last commit on #4858
- Assignee changed from Chris Buechler to Luiz Souza
Luiz apparently has a better fix.
- Status changed from Resolved to Assigned
- Status changed from Assigned to Resolved
This is now fixed. Thanks!
Also available in: Atom
PDF