Bug #7271: Co-existence of unbound and BIND/named - pfSense Packages - pfSense bugtracker

Actions

Copy link

Bug #7271

closed

Co-existence of unbound and BIND/named

Added by Rolf Sommerhalder almost 8 years ago. Updated over 3 years ago.

Status:

Resolved

Priority:

Normal

Assignee:

Jim Pingle

Category:

BIND

Target version:

Start date:

02/17/2017

Due date:

% Done:

100%

Estimated time:

Plus Target Version:

Affected Version:

2.4

Affected Plus Version:

Affected Architecture:

All

Description

Problem: both packages (want to) use same port 953 on 127.0.0.1 for (remote) control. If BIND is installed and enabled, then unbound fails to start after reboot.

2.4.0-BETA][admin@fwA]/root: /usr/local/sbin/unbound -c /var/unbound/unbound.conf
[1487326118] unbound[44792:0] error: can't bind socket: Address already in use for 127.0.0.1
[1487326118] unbound[44792:0] error: cannot open control interface 127.0.0.1 953
[1487326118] unbound[44792:0] fatal error: could not open ports

Implications of unbound failing to come up can be pretty drastic after restoring a config backup on a freshly installed pfSense box when its DNS Server Settings depend on unbound. It will try repeatedly to resolve beta.pfsense.com until timing out after minutes, be unable to install packages that are listed in the config backup, and fail to bring up SSHd or Web-configurator.

Proposed and tested solution: Move control port of unbound from 953 back to its default value 8953 (see [1]), e.g. in

/etc/inc/unbound.inc

replace:

 control-port: 953

by:

 control-port: 8953

Thanks,
Rolf

[1] https://www.freebsd.org/cgi/man.cgi?unbound.conf
...
control-port: port number
The port number to listen on for IPv4 or IPv6 control interfaces,
default is 8953. If you change this and permissions have been
dropped, you must restart the server for the change to take
effect.

Actions

Copy link

Updated by Kill Bill almost 8 years ago

Yeah, I'd definitely rather move the BIND control port than mess with default ports for a default pfSense resolver that's been there for ages without any issues.

Actions

Copy link

Updated by Jim Pingle almost 8 years ago

Target version deleted (~~2.4.0~~)

Agreed. Move the BIND port instead.

Actions

Copy link

Updated by Jim Pingle almost 8 years ago

Project changed from pfSense to pfSense Packages
Category changed from DNS Resolver to BIND

Actions

Copy link

Updated by Jim Thompson almost 8 years ago

Assignee set to Jim Pingle
Priority changed from High to Normal
Target version set to 2.4.0

Actions

Copy link

Updated by David Wood over 7 years ago

The work-round I used back in the days of the pfSense 2.2.x BIND port was to call rndc-confgen with the "-p <control port>" option. I believe that is all that is needed here.

Actions

Copy link