> The directory is writable. I run bind chrooted and the directory exists, > is owned by the named user and is writable by the named user.
But you don't have managed-keys or dnssec-lookaside auto configured, right? I was confused, and thought you did. If you had, that would mean this bug was fairly serious, because it would mean your managed keys weren't stored permanently. My statement about the expected behavior (i.e., that you'd see this log message only on the first start, and not thereafter) turns out to be true only if there's actually a managed key that needs maintaining. If you don't have any such keys, named won't create a file to save them in--but, oops, it still tries to load the file on startup, and so it always logs the "file not found" message. This is essentially a cosmetic bug, and will be fixed in a future release. You can work around it, as others have mentioned, by touching the file so that named will shut up, or you can ignore it. Thanks for your help with it. -- Evan Hunt -- e...@isc.org Internet Systems Consortium, Inc. _______________________________________________ bind-users mailing list bind-users@lists.isc.org https://lists.isc.org/mailman/listinfo/bind-users
