-
Notifications
You must be signed in to change notification settings - Fork 778
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unbound whitelist isn't working in v25 #8273
Comments
I can confirm that whitelisting e.g. 00fun.com does not work in 24.7.12_4 and 25.1. |
Not in my case: no domain can be whitelisted. |
try .*beer |
Most times I need to "Apply" and restart Unbound to whitelist a domain. Have you tried that? |
I am also experiencing similar issue with hagezi block list on opnsense 25.1. For example unable to access Facebook - adding Facebook.com, graph.facebook.com, web.facebook.com, and its cname in whitelist still blocks those addresses. Restarted the service, even restarted the firewall, don’t see any related error on unbound logs so I just turned off one of the hagezi lists that was blocking Facebook for now |
I have tried that, yes. Still no way to unblock anything. For example, whenever I try to update fedora 41 I get this:
I have confirmed it's Hagezi's Badware Hoster list the one blocking the domain I then go to Unbound > Whitelist > type
Not working! :( |
Regular expression like (.)?(.)? seems to work. (.)?(.)?apple.com allows the apple visual search on new iPhone which was blocked by Hagezi DOH list |
Unfortunately this is not a permanent solution. This issue should be investigated further. |
The regex workaround doesn't work for me. I'm on 25.1 |
I have same issue on 25.1. |
Another observation: All changes to the blocklists, and exceptions show up as expected in Example:
Resolving custom_pattern_10 to 12 (added on 24.7) is no problem at all, but the P0 blog ( I couldn't find any code that handles this file, but I found |
Important notices
Before you add a new report, we ask you kindly to acknowledge the following:
Describe the bug
Allowlists (whitelists) fail to bypass blocklists in DNS filtering. Explicitly allowed domains remain blocked if they match an active blocklist entry.
Example: Whitelisting
0.beer
(or any other) while using Hagezi Ultimate blocklist still prevents domain resolution (nslookup fails) unless the blocklist is disabled.To Reproduce
Steps to reproduce the behavior:
Services > Unbound > Blocklist
Whitelist
0.beer
(or any other) and save (use regex or regular domains)nslookup 0.beer
ordig 0.beer
Expected behavior
Allowlisted domains should override blocklist entries, permitting resolution of specified domains.
Actual behavior
Allowlisted domains remain blocked when present in active blocklist.
Workarounds tested
Relevant log files
Environment
Software version:
OPNsense 25.x (amd64)
Hagezi Blocklist Ultimate
Additional context
0.beer
confirmed present in Hagezi blocklistThe text was updated successfully, but these errors were encountered: