isc stork agent and named chroot

[Matthijs Mekking]

Hi Vladimir,

I bet it is something about stork looking for the named.conf file in a 
specific location, but you may want to resend your message to stork-users:

https://lists.isc.org/mailman/listinfo/stork-users

Best regards,

Matthijs

On 1/27/23 13:51, Vladimir Nikolic via bind-users wrote:
> Hi,
> 
> Looks like stork agent doesn't work in a named chroot environment.
> On one of my systems, it complains about non-existing config file:
> 
> stork-agent[129190]: time="2023-01-27 04:47:07" level="warning" 
> msg="cannot parse BIND 9 config file /etc/named.conf: exit status 1; 
> /etc/named.conf:8: open: /etc/named.conf.inc: file not found\n" file=" 
>           bind9.go:398  "
> 
> Although /var/named/chroot/etc/named.conf.inc file exists and named is 
> working without issues.
> OS is CentOS 7 and bind-chroot rpm version is 9.11.4-26.P2.el7_9.10.
> 
> Regards,
> Vladimir