I”m running it as named-chroot, and named is rw permissions at the /var/named
This is the directory listing: [root@mydns named]# ls -l total 16 drwxr-x---. 7 named named 61 Oct 9 13:30 chroot drwxrwx---. 2 named named 127 Feb 28 03:27 data drwxrwx---. 2 named named 60 Mar 4 13:57 dynamic drwxr-xr-x. 2 named named 31 Mar 2 13:46 log -rw-r-----. 1 named named 2253 Sep 9 09:48 named.ca<http://named.ca> -rw-r-----. 1 named named 152 Sep 9 09:48 named.empty -rw-r-----. 1 named named 152 Sep 9 09:48 named.localhost -rw-r-----. 1 named named 168 Sep 9 09:48 named.loopback drwxrwx---. 2 named named 6 Sep 9 09:47 slaves On Mar 5, 2021, at 12:19 PM, Gregory Sloop <gr...@sloop.net<mailto:gr...@sloop.net>> wrote: You may need to set permissions on not just the files, but the directory too. If it didn't have permissions to existing files, I suspect the parent directory doesn't allow that same user/group to create files either - so the jnl files don't get created. -Greg BJ> Fixing the permissions and restarting named got dynamic updating BJ> working again, but new systems (ie names that are NOT already in BJ> the Zone file ) are throwing errors about the journal file: error: BJ> journal open failed: unexpected error BJ> Mar 5 11:44:34 mydns named[45631]: client @0x7fa31f4178d0 BJ> 10.128.206.151#58512: updating zone 'DYN.Zone.COM/IN':<http://DYN.Zone.COM/IN':> deleting BJ> rrset at 'dhbfswrkgrps1.DYN.Zone.COM<http://dhbfswrkgrps1.DYN.Zone.COM>' AAAA BJ> Mar 5 11:44:34 mydns named[45631]: client @0x7fa31f4178d0 BJ> 10.128.206.151#58512: updating zone 'DYN.Zone.COM/IN':<http://DYN.Zone.COM/IN':> deleting BJ> rrset at 'dhbfswrkgrps1.DYN.Zone.COM<http://dhbfswrkgrps1.DYN.Zone.COM>' A BJ> Mar 5 11:44:34 mydns named[45631]: client @0x7fa31f4178d0 BJ> 10.128.206.151#58512: updating zone 'DYN.Zone.COM/IN':<http://DYN.Zone.COM/IN':> adding an BJ> RR at 'dhbfswrkgrps1.DYN.Zone.COM<http://dhbfswrkgrps1.DYN.Zone.COM>' A 10.128.206.151 BJ> Mar 5 11:45:27 mydns named[45631]: client @0x7fa31f3f7c20 BJ> 128.196.45.228#49190: updating zone 'DYN.Zone.COM/IN':<http://DYN.Zone.COM/IN':> deleting BJ> rrset at 'NIC-COPIT.DYN.Zone.COM<http://NIC-COPIT.DYN.Zone.COM>' AAAA BJ> Mar 5 11:45:27 mydns named[45631]: client @0x7fa31f3f7c20 BJ> 128.196.45.228#49190: updating zone 'DYN.Zone.COM/IN':<http://DYN.Zone.COM/IN':> deleting BJ> rrset at 'NIC-COPIT.DYN.Zone.COM<http://NIC-COPIT.DYN.Zone.COM>' A BJ> Mar 5 11:45:27 mydns named[45631]: client @0x7fa31f3f7c20 BJ> 128.196.45.228#49190: updating zone 'DYN.Zone.COM/IN':<http://DYN.Zone.COM/IN':> adding an BJ> RR at 'NIC-COPIT.DYN.Zone.COM<http://NIC-COPIT.DYN.Zone.COM>' A 128.196.45.228 BJ> Mar 5 11:45:27 mydns named[45631]: client @0x7fa31f3f7c20 BJ> 128.196.45.228#49190: updating zone 'DYN.Zone.COM/IN':<http://DYN.Zone.COM/IN':> error: BJ> journal open failed: unexpected error BJ> Is there a specific command to create the .jnl file? I thought BJ> named created it automatically as needed. (at least the BJ> named-journalprint man page indicates this…) -- Bruce Johnson University of Arizona College of Pharmacy Information Technology Group Institutions do not have opinions, merely customs
_______________________________________________ Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe from this list ISC funds the development of this software with paid support subscriptions. Contact us at https://www.isc.org/contact/ for more information. bind-users mailing list bind-users@lists.isc.org https://lists.isc.org/mailman/listinfo/bind-users
