Evan: > 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. >
that makes sense. It did go away when I set up lookaside properly, and I thought I knew how to make it go away. Then I reconfigured (as a test) without lookaside (or any dnssec features enabled for that matter) and the problem returned. I agree it is cosmetic and we can live with it. Thank you _______________________________________________ bind-users mailing list bind-users@lists.isc.org https://lists.isc.org/mailman/listinfo/bind-users
