Date: Sun, 18 Feb 2024 05:39:48 +0900 From: Tatsuki Makino <tatsuki_makino@hotmail.com> To: bob prohaska <fbsd@www.zefox.net>, freebsd-ports@freebsd.org Cc: Moin Rahman <bofh@freebsd.org> Subject: Re: Bind918 slave reports Dumping master file...open: file not found Message-ID: <SI2PR01MB503694DEC890D5170CDE845FFA532@SI2PR01MB5036.apcprd01.prod.exchangelabs.com> In-Reply-To: <CD32FE07-A050-42CF-A91C-342B90A583B7@freebsd.org> References: <ZdD6cqD8Sc59%2Bn%2Bk@www.zefox.net> <CD32FE07-A050-42CF-A91C-342B90A583B7@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Hello. It would be easier for later visitors to understand if the background of the "working" directory were also explained. Moin Rahman wrote on 2024/02/18 03:34: >> On Feb 17, 2024, at 7:26 PM, bob prohaska <fbsd@www.zefox.net> wrote: >> The options section of named.conf contains: >> directory "/usr/local/etc/namedb/working"; > > Do you have a directory named `slave` under `/usr/local/etc/namedb/working` ? First, this directory is just to avoid the warning that occurs at https://gitlab.isc.org/isc-projects/bind9/-/blob/366b93f83565902aa98b3e146e0ead88e7502d87/bin/named/server.c#L9228 For this we will be asked to write a configuration file that takes into account that the working directory is there. In named.conf.sample, everything is replaced with absolute paths. Since absolute paths are long, we want to use relative paths to make things easier :) So since all the provided directories are at the same level as the "working" directory, they need to be written with relative paths such as ../slave. and/or ../secondary.. Is this an acceptable explanation? :) Regards.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?SI2PR01MB503694DEC890D5170CDE845FFA532>