BIND won't start after upgrade to 23.1

[pilotboy72]

Hello,


The Bind service (NAMED) will not start after upgrading to 23.1.  Attempting to start the service from the GUI, the screen comes back almost immediately and the service does not start.  There are no logs.


I tried this from the command line (service named start) and I see the following error:

/usr/local/etc/namedb/named.conf:92: /usr/local/lib/named/filter-aaaa.so: plugin check failed: failure
/usr/local/etc/rc.d/named: ERROR: named-checkconf for /usr/local/etc/namedb/named.conf failed


On that line of the file, I see the following:


plugin query "/usr/local/lib/named/filter-aaaa.so" {
                   filter-aaaa-on-v4 yes;
           };

I can remove those three lines and the service starts.

Clicking on Services > Bind > Configuration > Disable IPV6 brings back the problem of the service not starting, but removing (unchecking) it does not fix the problem.

Anyone seen anything similar?

[franco]

Good lord, I don't really understand why bind/isc devs are trying to break their configuration so hard on upgrades:

https://github.com/opnsense/plugins/commit/7205ea00948f

# opnsense-patch -c plugins 7205ea00948f

(and reapply your configuration)


Cheers,
Franco

[pilotboy72]

Good lord, I don't really understand why bind/isc devs are trying to break their configuration so hard on upgrades:

https://github.com/opnsense/plugins/commit/7205ea00948f

# opnsense-patch -c plugins 7205ea00948f

(and reapply your configuration)


Cheers,
Franco

Looks like that fixed it thanks.

[franco]

Thanks! I'm considering a hotfix, but not before Monday in case something else pops up.


Cheers,
Franco

[pilotboy72]

Makes sense.  Not sure how much of the user base uses Bind, but I find it the best way to create and manage my own domain(s).

[cookiemonster]

I imagine Herr Hausen will be interested.

[Patrick M. Hausen]

Thanks for the heads up  8)