Netgate Discussion Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Search
    • Register
    • Login
    Introducing Netgate Nexus: Multi-Instance Management at Your Fingertips.

    DNS Resolver (Unbound) won't start

    Scheduled Pinned Locked Moved DHCP and DNS
    3 Posts 2 Posters 1.4k Views 2 Watching
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • R
      rsterenborg
      last edited by

      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?

      Thanks!

      1 Reply Last reply
      Reply Quote 0
      • johnpozJ
        johnpoz LAYER 8 Global Moderator
        last edited by johnpoz

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

        https://redmine.pfsense.org/issues/7271

        An intelligent man is sometimes forced to be drunk to spend time with his fools
        If you get confused: Listen to the Music Play
        Please don't Chat/PM me for help, unless mod related
        SG-4860 26.07 | Lab VMs 2.9.0, 26.07

        1 Reply Last reply
        Reply Quote 0
        • R
          rsterenborg
          last edited by

          The issue is still in there then.

          https://github.com/pfsense/FreeBSD-ports/commit/5fb1095cd2a5949f9f44fc985c0fe8aab77185ef.patch

          I applied the patch and things started working:

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

          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!

          1 Reply Last reply
          Reply Quote 0

          Hello! It looks like you're interested in this conversation, but you don't have an account yet.

          Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.

          With your input, this post could be even better 💗

          Register Login
          • First post
            Last post
          Copyright 2026 Rubicon Communications LLC (Netgate). All rights reserved.
          Privacy Policy · Cookie Policy