Re: [cobalt-users] Named Error in Secondary DNS

["Landon Jenkins" <landonak@xxxxxxxxxxx>]

>> 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
>
>
> check to see if you have a directory /etc/named
> and see if named has permissions to write to it.
>
> look at /etc/named.conf options container: (mine)
> options {
>         directory "/etc/named";
>         allow-transfer { ip.ad.re.ss1; ip.ad.re.ss2; };
>         version "my name server";
>         listen-on { ip.ad.re.ss3; ip.ad.re.ss4; 127.0.0.1; };
> };
>
> important part is directory "/etc/named"

My named.conf looks fine.

Here is the folder information:

drwxr-xr-x   2 root     root         3072 Mar 11 08:57 named

I'm thinking this may have something to do with the recent 2.0
upgrade/running named instead of root in bind. Is it safe to chown the named
directory to the user 'named' as it already is on my RAQ3?

Landon