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.
I created a feature request and a pull request:
https://github.com/opnsense/plugins/issues/4773
https://github.com/opnsense/plugins/pull/4774
Quote from: nick2253 on June 26, 2025, 02:21:30 AMI created a feature request and a pull request:
https://github.com/opnsense/plugins/issues/4773
https://github.com/opnsense/plugins/pull/4774
Thanks for this, Nick.
I presume issue #4773 will be closed as PR #4775 (https://github.com/opnsense/plugins/pull/4775) merged about a month ago.
Custom
options statements appear to be a definite no-go (I believe this would require an
include directive within the
options block)... 8^(
I'll have to raise a couple of PRs...