Then this is your problem. Under Linux, (which I'm assuming you're using
because of your mention of chattr), named will drop all root priveleges
after startup, including the ability to write to any directory, regardless
of the attributes.
-Tim
On Fri, 27 Dec 2002, Emmanuel A. Nnko wrote:
> Dear Tim and All,
>
> Thanks for your prompt response.
>
> Yes!
>
> But might it be because of 'chroot'ing of the DNS as I have restricted
> writing on the directory by this command: 'chattr +i'...
>
> Thanks again,
>
> Emmanuel
>
> Tim Maestas wrote:
>
> >Does the user that named is running as have permission to write to the
> >working directory of named and the directory of the zone files?
> >
> >-Tim
> >
> >On Fri, 27 Dec 2002, Emmanuel A. Nnko wrote:
> >
> >
> >
> >>Dear Bind-users,
> >>
> >>I am currently running two DNSes servers i.e Primary/Master and
> >>Secondary/Slave servers. For a week or two both were operating OK. I am
> >>using Bind 9.2.1
> >>
> >>But recently I am having a problem with the Secondary/Slave DNS on the
> >>updating entries from Masters. On the log (attached below) for both
> >>Primary/Master and Secondary/Slave servers shows as they are doing IXFR
> >>for the changes made on the zone in Primary/Master but at the end the
> >>transters to the secondary fails.
> >>
> >>The attached logs are for secondary/slave nameserver.
> >>
> >>############################## Logs #######################################
> >>
> >> dumping master file: tmp-XXXX0mPbem: open: permission denied: 1 Time(s)
> >> dumping master file: tmp-XXXX1IADe0: open: permission denied: 1 Time(s)
> >> dumping master file: tmp-XXXX39ibL4: open: permission denied: 1 Time(s)
> >> dumping master file: tmp-XXXX5fNMHg: open: permission denied: 1 Time(s)
> >> dumping master file: tmp-XXXX6HsOYg: open: permission denied: 1 Time(s)
> >> dumping master file: tmp-XXXX9SS4tr: open: permission denied: 1 Time(s)
> >> dumping master file: tmp-XXXXBOghNO: open: permission denied: 1 Time(s)
> >> dumping master file: tmp-XXXXBZJIpZ: open: permission denied: 1 Time(s)
> >> dumping master file: tmp-XXXXBke0Ci: open: permission denied: 1 Time(s)
> >> .....
> >> .....
> >>
> >> transfer of '94.58.209.in-addr.arpa/IN' from primary.name.server#53:
> >>end of transfer: 28 Time(s)
> >> transfer of '94.58.209.in-addr.arpa/IN' from primary.name.server#53:
> >>failed while receiving responses: permission denied: 28 Time(s)
> >> transfer of 'ttcldata.net/IN' from primary.name.server#53: end of
> >>transfer: 28 Time(s)
> >> transfer of 'ttcldata.net/IN' from primary.name.server#53: failed
> >>while receiving responses: permission denied: 28 Time(s)
> >> zone bluebay.co.tz/IN: refresh: failure trying master
> >>primary.name.server#53: timed out: 1 Time(s)
> >> zone cidapsu.or.tz/IN: refresh: failure trying master
> >>primary.name.server#53: timed out: 1 Time(s)
> >> zone ttcl.co.tz/IN: refresh: failure trying master
> >>primary.name.server#53: timed out: 1 Time(s)
> >> zone ttcldata.net/IN: refresh: failure trying master
> >>primary.name.server#53: timed out: 1 Time(s)
> >> ...............
> >> ............
> >>
> >>################################################################################
> >>
> >>Please advise on how to rectify the above anomaly.
> >>
> >>Thank you in advance.
> >>
> >>With festive regards,
> >>
> >>Emmanuel
> >>
> >>
> >>
> >>
> >>
> >
> >
> >
> >
>
>
>
>
|
