"
I created a feature request and a pull request:
https://github.com/opnsense/plugins/issues/4773
https://github.com/opnsense/plugins/pull/4774
https://github.com/opnsense/plugins/issues/4773
https://github.com/opnsense/plugins/pull/4774
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.
Pages1
#1
25.1, 25.4 Production Series / Re: os-bind plugin - Any way to run custom directives?
June 26, 2025, 02:21:30 AM #2
25.1, 25.4 Production Series / os-bind plugin - Any way to run custom directives?
June 25, 2025, 07:36:06 PM
I'm using BIND as a DNS server for my DMZ, and I'm replicating the relevant zone from my main Windows DNS server. We discovered a bug with EDNS AXFR transfers out of Windows (I'm currently working with ISC and Microsoft to fix this), but in the meantime, I need to disable EDNS queries from BIND to the main DNS server.
The easy way to do this is to add a server directive to the config: server 1.2.3.4 { edns no; };
However, there doesn't appear to be a way to add the server directive directly, or to add custom directives to the config. If I manually add it to the named.conf file, then it gets over-written when anyone makes a modification to the BIND config.
I feel like it would be a great feature to be able to add custom directives, so that way if anyone in the future needs something, or if BIND adds new directives that aren't present in the GUI, they can easily add them in a way that always retains them.
Alternatively, if you add an includes statement that includes a named.local.conf files, then we could edit that file if we need anything custom.
The easy way to do this is to add a server directive to the config: server 1.2.3.4 { edns no; };
However, there doesn't appear to be a way to add the server directive directly, or to add custom directives to the config. If I manually add it to the named.conf file, then it gets over-written when anyone makes a modification to the BIND config.
I feel like it would be a great feature to be able to add custom directives, so that way if anyone in the future needs something, or if BIND adds new directives that aren't present in the GUI, they can easily add them in a way that always retains them.
Alternatively, if you add an includes statement that includes a named.local.conf files, then we could edit that file if we need anything custom.
#3
25.1, 25.4 Production Series / Re: update OPNsense 25.1.6-amd64 -> had to run it twice again for bind and postfix
June 25, 2025, 07:23:43 PM
I noticed something similar. I wish I would have documented it, but I failed to do so.
After the upgrade, I noticed that BIND wasn't worked. When I tried to use dig, it told me that a dependency wasn't install. Reinstalling the BIND package fixed the problem. As best as I can recall, it was three of the BIND *.so files that were missing (presumably deleted as part of the update).
After the upgrade, I noticed that BIND wasn't worked. When I tried to use dig, it told me that a dependency wasn't install. Reinstalling the BIND package fixed the problem. As best as I can recall, it was three of the BIND *.so files that were missing (presumably deleted as part of the update).
Pages1
