OPNsense Forum
Archive => 20.1 Legacy Series => Topic started by: youngman on April 10, 2020, 08:34:22 am
-
G'day All,
Has been a while since I played with OPNsense. It has been running like a champ. However, I have recently updated to 20.1.4 and note that there has been some discussion on Unbound's Custom Options field regarding its [future] removal.
I've managed to swap over to mimugmail's unbound-plus, which has removed the need for one line from my custom options re DNS filtering (great job mimugmail).
However, at the risk of looking like an idiot, I'm hoping someone can tell me where my other few lines need to be 'moved' to in order to clear the custom options while retaining the same functionality. Hopefully simple and obvious to one of the in-house experts!
server:private-address: 127.0.0.0/8
## include:/var/unbound/blacklist.conf
local-data: "local.lan. 10800 IN SOA opnsense.local.lan. root.local.lan. 1 3600 1200 604800 10800"
Thanks in advance,
Guv
P.s. Is # the correct way to comment out the custom options??
-
Can you Open a feature request in GitHub please? I can add it at some time.
-
G'day mimugmail,
Not sure which part of my query would require a GitHub feature request? Perhaps the local-data SOA line?
As far as my own example, the first line appears to be redundant. The defaults listed in /var/unbound/unbound.conf appear to cover this and many other private addresses.
The local-data part I've also commented out without any apparent ill effect. I use IP addresses internally anyway - so no need for this in my use case either I don't think...
Can also confirm that yes, hashes are the correct method to comment out in unbound.conf (and therefore also work in the custom parameters box).
Cheers,
Guv
-
It's just that I dont forget it since Forum thread are lost very fast ;)