Bug #5441
closed
Unbound config does not bind to CARP IP
100%
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.
Updated by Chris Buechler over 8 years ago
- 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.
Updated by Renato Botelho over 8 years ago
- 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
Updated by Jeremy Porter over 8 years ago
I can retest, but this only happened on upgrade
Updated by Renato Botelho over 8 years ago
- Status changed from Feedback to Assigned
Nevermind, I'll test it on upgrade then
Updated by Renato Botelho over 8 years ago
- Assignee changed from Renato Botelho to Luiz Souza
Probably another side-effect of #4858
Updated by Luiz Souza over 8 years ago
- Status changed from Assigned to Feedback
- % Done changed from 0 to 100
Updated by Tobias Wigand over 8 years ago
Also upgraded, from 2.2.6 to 2.3BETA from today.
https://forum.pfsense.org/index.php?topic=105451.0
Only one of 4 CARP IPs is selectable, the other 3 do not appear.
Updated by Renato Botelho over 8 years ago
- Status changed from Feedback to Assigned
Updated by Chris Buechler about 8 years ago
- Status changed from Assigned to Resolved
- Assignee changed from Luiz Souza to Chris Buechler
this was fixed by my last commit on #4858
Updated by Jim Thompson about 8 years ago
- Assignee changed from Chris Buechler to Luiz Souza
Updated by Jim Thompson about 8 years ago
- Status changed from Resolved to Assigned
Updated by Luiz Souza about 8 years ago
- Status changed from Assigned to Resolved
This is now fixed. Thanks!