Re: bin/30420: chrooted named does not work out of the box.

["Jeremy C. Reed via gnats" <gnats-admin%NetBSD.org@localhost>]

The following reply was made to PR bin/30420; it has been noted by GNATS.

From: "Jeremy C. Reed" <reed%reedmedia.net@localhost>
To: gnats-bugs%gnats.NetBSD.org@localhost
Cc: 
Subject: Re: bin/30420: chrooted named does not work out of the box.
Date: Fri, 8 May 2026 22:41:03 +0000 (UTC)

 It appears the changes proposed in this ticket were applied and then 
 since then further improvements to handle the copying for the files for 
 chroot environment.
 
 But new problem:
 
 May  8 22:34:20 t1 named[27559]: invalid managed-keys-directory keys: 
 file not found
 
 If named_chrootdir is defined on first run of the rc.d script then no 
 keys directory.
 This solved it for me:
 
 +       if [ ! -d "/etc/namedb/keys" ]; then
 +               mkdir -m 775 "/etc/namedb/keys"
 +               chown named:named "/etc/namedb/keys"
 +       fi
 +
          if [ -z "$named_chrootdir" ]; then
 -               if [ ! -d "/etc/namedb/keys" ]; then
 -                       mkdir -m 775 "/etc/namedb/keys"
 -                       chown named:named "/etc/namedb/keys"
 -               fi
                  return 0;
          fi