[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [cobalt-users] Named Error in Secondary DNS - RESOLVED
- Subject: Re: [cobalt-users] Named Error in Secondary DNS - RESOLVED
- From: "Landon Jenkins" <landonak@xxxxxxxxxxx>
- Date: Tue Mar 19 09:07:01 2002
- List-id: Mailing list for users to share thoughts on Cobalt products. <cobalt-users.list.cobalt.com>
Landon Jenkins wrote...
>> Here's a snip of what happens when starting named...
>>
>> Mar 6 14:12:59 ns2 named[551]: Forwarding source address is
[0.0.0.0].1024
>> Mar 6 14:12:59 ns2 named[552]: group = 25
>> Mar 6 14:12:59 ns2 named[552]: user = named
>> Mar 6 14:12:59 ns2 named[552]: Ready to answer queries.
>> Mar 6 14:12:59 ns2 named-xfer[557]: can't make tmpfile
>> (sec.domain.com.OfqLRa): Permission denied
>> Mar 6 14:12:59 ns2 named-xfer[558]: can't make tmpfile
>> (sec.domain.com.zOz7Da): Permission denied
>> Mar 6 14:12:59 ns2 named-xfer[559]: can't make tmpfile
>> (sec.domain.com.cXxVAc): Permission denied
This has been resolved. It turns out that after installing the OS2 update,
the named user account writes these zone records instead of root. Upon
further inspection, /etc/named was owned by root, therefore not allowing any
creation or modification of files by named.
chown named /etc/named did the trick.
Thanks to Dan and everyone else for your suggestions!
Landon