Menu

Show posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Show posts Menu

Messages - bs-opn

#1
Thanks for the recommendation. Unfortunately, Unbound wants a Network Interface to listen to for requests. Bind wants an IP address. Is there an easy way to get unbound to use an IP Alias? I think that would solve what I'm trying to do.

I'm trying to stick with a solution that keeps everything in the config.xml so it doesn't get overwritten whenever I make a change through the GUI.
#2
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;
    };