Project

General

Profile

Actions
Copy link

Bug #5441

closed

Unbound config does not bind to CARP IP

Added by Jeremy Porter about 9 years ago. Updated almost 9 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
Luiz Souza
Category:
DNS Resolver
Target version:
2.3
Start date:
11/13/2015
Due date:
% Done:

100%

Estimated time:
Plus Target Version:
Release Notes:
Affected Version:
2.3
Affected Architecture:

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.

Actions
Copy link

Also available in: Atom PDF