Bug #10413
closedBIND plugins are not copied into chroot
100%
Description
BIND 9.13.5 introduced a new plugin system, and the filter-aaaa support was moved to a plugin, so we need to copy the plugins into the chroot to allow using this feature. Previously, "filter-aaaa-on-v4 yes;
" was a built-in option to filter out AAAA records when queried via an IPv4 socket, but this filtering was out to a plugin. To perform the same functionality, you need to add a custom option to your views (since the filter plugins must be declared in views, if they are used):
plugin query "filter-aaaa.so" { filter-aaaa-on-v4 yes; };
Currently, this fails because the "filter-aaaa.so
" file is not found. BIND expects there to be "named
" directory in ${libdir}
that contains plugins, which on our package computes out to "/usr/local/lib/named
". However, the pfSense BIND package runs from the "/cf/named
" chroot, so we need to copy those plugins into that chroot to allow their use.
Related issues