-
Notifications
You must be signed in to change notification settings - Fork 746
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.
- When the request is meant for an existing plugin, I've added its name to the title.
Is your feature request related to a problem? Please describe.
Thanks for adding the forward only zone options to the dns/bind plugin. It needs an option to allow setting the "forward only" tag on a zone though. The default for a forward domain is forward first, but will still check upstream servers. If you define a forward zone for a reverse zone, it will fail even if local forward servers respond with valid response, without this tag.
Describe the solution you'd like
A clear and concise description of what you want to happen.
(e.g. I would like an input field in the /ui/firewall/alias which would add .... to ....)
Add a checkbox to forward only zone configuration to tag zone with "forward only" or make it default. I personally have never used forward type zone without it. Either forward or reverse.
I was able to test by manually editing /usr/local/etc/namedb/named.conf, adding the "forward only;" line to one of my reverse zones, and doing a kill -s 1 to the bind process at which point the forward reverse zone successfully resolves.
zone "5.9.10.in-addr.arpa" {
type forward;
forward only;
forwarders { 10.9.5.11; 10.9.5.15; };
};
Additional context
Add any other context or screenshots about the feature request here.
