1
Development and Code Review / BIND plugin configuration
« on: August 09, 2019, 07:27:23 pm »
I am trying to transition from pfSense to OPNsense and I'm trying to get the pfBlocker functionality replicated.
I currently have Unbound DNS running on port 5053. I have bind running on port 53.
I can modify the /usr/local/etc/namedb/named.conf to specify a port for a forwarder, but I can't do that in the UI. Any changes in the UI will overwrite my changes to the named.conf.
My apologies for the basic question, but what is the best way of making an enhancement request to allow the UI forwarder input validation to allow specifying a port that gets broken out in the named.conf as:
// Unbound listens on 5053 and forwards to CloudFlare via DNS-TLS
forwarders {
127.0.0.1 port 5030;
};
I currently have Unbound DNS running on port 5053. I have bind running on port 53.
I can modify the /usr/local/etc/namedb/named.conf to specify a port for a forwarder, but I can't do that in the UI. Any changes in the UI will overwrite my changes to the named.conf.
My apologies for the basic question, but what is the best way of making an enhancement request to allow the UI forwarder input validation to allow specifying a port that gets broken out in the named.conf as:
// Unbound listens on 5053 and forwards to CloudFlare via DNS-TLS
forwarders {
127.0.0.1 port 5030;
};