Hi folks,
I had an issue after upgrading to 26.1.6 where unbound switched it's default access list changed from Allow to Deny following the upgrade.
I don't think this is specifically related to the 26 series, but I didn't see a forum for generalized bug reports. Figured it best to post and look for ideas. It looks like someone else has had this happen around a year ago https://blog.ewonchang.com/2025/06/08/strange-issue-on-opnsense-with-unbound-dns/ and then 1 other person according to the comments on this blog (I am Alice)
Any thoughts or advice to contribute debug wise and I'd be willing to help find where this edge case is coming from.
Quote from: Au on April 14, 2026, 06:17:40 PMbut I didn't see a forum for generalized bug reports
Bug reports should go into Github issues.
Upgrading to 26.1.6 from which version? It's been ages since we changed ACL for Unbound:
community/23.7/23.7:o unbound: rewrote general settings and ACL handling using MVC/API
Cheers,
Franco
From 26.1.5
Should I convert this to an issue on github? I was unaware that there was a github repository - I'd imagine this belongs in core?
Yes but it makes no sense from the data points that have been added so far. If you suspect that a change to config.xml was made then the first thing you do is go to System: Configuration: History and find where the change was made by which component. With this we can evaluate. Without this basic information it's hard to check anything.
Cheers,
Franco
for continuity of discussion, I've opened the thread on github https://github.com/opnsense/core/issues/10155
We can lock this post, and see if there is anything more I can look to add on githubs issues. I've been unsuccessful trying to reproduce with the previous snapshot I had.