Re: Authoritative and caching

2025-03-16 Thread Danjel Jungersen via bind-users
On 16-03-2025 21:40, Greg Choules wrote: Hi. From what others have said, that makes sense. For BIND's static files to be under /etc and operational files (zone data, journals etc.) to be somewhere else. What are the permissions on /var/lib/bind/ and/or /var/cache/bind? Both is root:bind and

Re: Authoritative and caching

2025-03-16 Thread Danjel Jungersen via bind-users
>I would either change ownership of "/etc/bind" and all files and folders >below that from "root" to "bind", or, if the group for user "bind" is also >"bind", leave ownership as root but change group permissions to rwx for >everything "/etc/bind" and below. You could try starting with just >"/et

Re: Authoritative and caching

2025-03-16 Thread Ondřej Surý
It does, and it follows the FHS, so not in /etc. Ondrej -- Ondřej Surý — ISC (He/Him) My working hours and your working hours may be different. Please do not feel obligated to reply outside your normal working hours. > On 16. 3. 2025, at 17:08, Timothe Litt via bind-users > wrote: > > In the

Re: Authoritative and caching

2025-03-16 Thread Timothe Litt via bind-users
On 15-Mar-25 18:16, Lee wrote: On Sat, Mar 15, 2025 at 5:25 PM Danjel Jungersen via bind-users wrote: Apparmor was also mentioned, I have no experience with that, and have not changed it in any way (to my knowledge)... On my machine, $ journalctl -l | grep apparmor | grep bind |more shows m

Re: Authoritative and caching

2025-03-16 Thread Greg Choules via bind-users
Sending from the correct alias this time! On Sun, 16 Mar 2025 at 09:03, Greg Choules wrote: > Thank you. > The problem is that named is running as user "bind" but that user > doesn't have file system permissions to create and write to files (the .jnl > and .jbk files at least) in places that it