You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
We are using the Unbound service and are forwarding an Active Directory dns zone to the designated samba dns server. Additionally we want to use the Rebind Protection feature of Unbound in Opnsense, to filter a private subnet out of the returned addresses.
Unfortunately all forwarding rules create an entry for private-domain (see:
{% for forward in helpers.toList('OPNsense.unboundplus.dots.dot') %}
)
Describe the solution you like
I would like a checkbox in the /ui/unbound/forward > Edit rule dialog, which can be defaultly enabled (for backwards compatibility), to enable
Describe alternatives you considered
I tried to override the private-address option with a custom config file, but seems not to be possible, as unbound is merging entries
Current workaround is to disable the unbound forward rules inside the UI, and add a custom config file at /usr/local/etc/unbound.opnsense.d/forward.conf containing only the forward rules. Then the generated private_domains.conf file does not include any private-domain entry.
Additional context
I am not sure what the original reason is/was to always add forwarding domains to private-domains. So maybe the default can be discussed.
The text was updated successfully, but these errors were encountered:
Important notices
Before you add a new report, we ask you kindly to acknowledge the following:
Is your feature request related to a problem? Please describe.
We are using the Unbound service and are forwarding an Active Directory dns zone to the designated samba dns server. Additionally we want to use the Rebind Protection feature of Unbound in Opnsense, to filter a private subnet out of the returned addresses.
Unfortunately all forwarding rules create an entry for
private-domain
(see:core/src/opnsense/service/templates/OPNsense/Unbound/core/private_domains.conf
Line 10 in d09cb92
Describe the solution you like
I would like a checkbox in the
/ui/unbound/forward
> Edit rule dialog, which can be defaultly enabled (for backwards compatibility), to enableDescribe alternatives you considered
/usr/local/etc/unbound.opnsense.d/forward.conf
containing only the forward rules. Then the generatedprivate_domains.conf
file does not include any private-domain entry.Additional context
I am not sure what the original reason is/was to always add forwarding domains to private-domains. So maybe the default can be discussed.
The text was updated successfully, but these errors were encountered: