DNS Resolver (Unbound) won't start

  • Hi,

    We're using: 2.4.3-RELEASE-p1 (amd64).

    I configured Bind to only listen on specific interfaces on port 5353. We need Bind to host a local DNS zone on this server and this works.

    Then I configured the DNS Resolver (Unbound) to run to support automatic DNS updates from the DHCP server. I want Unbound to forward queries which it can't answer to Bind. (Is there a way to have the DHCP server do updates to Bind? I may have overlooked how to do that in pfSense: if there is a way, please enlighten me.)

    However, the DNS Resolver does not start. I don't see any logging from Unbound, and the process list does not show an unbound process running.
    I can see that /var/unbound/unbound.conf has the correct configuration. If I use /usr/local/etc/rc.d/unbound on the commandline (which clearly isn't the way to do, but I wanted to try it anyway) then Unbound starts, and this shows up in the log, but it starts with incorrect configuration from /usr/local/etc/unbound/unbound.conf.
    I don't know how pfSense starts Unbound, but since there is no logging I suspect that pfSense does not actually start Unbound.

    So.. What is it that I'm doing wrong? Since I'm not seeing any logging when trying to start Unbound from the pfSense GUI I'm not convinced it's a configuration issue. Is there any other information needed from me to point me in the right direction?


  • Rebel Alliance Global Moderator

    I know there was/is an issue with the control port 953 when trying to run unbound and bind together


  • The issue is still in there then.


    I applied the patch and things started working:

    : sockstat | grep 953
    unbound  unbound    80331 18 tcp4         *:*
    bind     named      73689 24 tcp4        *:*

    Like stated in the issue I also would like to keep the control ports default (Bind: 953, Unbound: 8953), but for now this will work.

    Thanks a lot!