Netbird: Unbound does not restart
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 1.2k
- Forks
- 863
- Avg merge
- 2d 6h
- Merged PRs (30d)
- 10
Description
Important notices
Before you add a new report, we ask you kindly to acknowledge the following:
- I have read the contributing guide lines at https://github.com/opnsense/plugins/blob/master/CONTRIBUTING.md
- I have searched the existing issues, open and closed, and I'm convinced that mine is new.
- The title contains the plugin to which this issue belongs
Describe the bug
I have Unbound set to listen on my Netbird interface. This allows clients to use the OPNsense instance as their DNS Nameserver (set in Netbird server on the "Nameservers" page). However, Unbound does not pick up changes. This is an issue after reboot since Unbound may start before the Netbird connection is up.
To Reproduce
Steps to reproduce the behavior:
- Set Unbound to listen on the Netbird interface
- Reset Netbird connection (up/down/etc) or reboot
- Unbound not listening on Netbird interface
- Running
configctl unbound restartsolves the issue (temporarily)
Expected behavior
Unbound should listen on Netbird interface no matter how the connection changes.
Screenshots
N/A
Relevant log files
N/A
Additional context
N/A
Environment
OPNsense 26.1.11_6-amd64
FreeBSD 14.3-RELEASE-p16
OpenSSL 3.0.21
os-netbird 1.3_3
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the issue using the listed Netbird interface and Unbound steps, then trace the Netbird connection reset and reboot flow around the existing configctl unbound restart command. Done means Unbound automatically listens on the Netbird interface after the connection changes or comes up after reboot, without a manual restart.
Written by the indexing model from the issue text.
Assessment
- Domain
- networking
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100