Re: Named Issues after FC2 upgrade

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



> Message: 19
> Date: Sun, 20 Jun 2004 17:49:29 +0200
> From: Alexander Dalloz
> <alexander.dalloz@xxxxxxxxxxxxxxxx>
> Subject: Re: Named Issues after FC2 upgrade
> To: For users of Fedora Core releases
> <fedora-list@xxxxxxxxxx>
> Message-ID:
> <1087746569.3189.25.camel@xxxxxxxxxxxxxxxxxxxxx>
> Content-Type: text/plain; charset="us-ascii"
> 
> Am So, den 20.06.2004 schrieb edwarner99@xxxxxxxxx
> um 16:48:
> 
> > I'm having some issues with named after I upgraded
> > from FC1 to FC2.
> > I changed the persmissions to R/W, that didn't
> work.
> > Then I  changed ownership to root with R/W.
> > That didn't work either. 
> > Any suggestions?
> > Thanks,
> > 
> > 
> > Jun 20 10:37:21 bonsai named[5196]: dumping master
> > file: tmp-XXXXViGJwT: open: permission denied
> > Jun 20 10:37:21 bonsai named[5196]: zone
> > 100.168.192.in-addr.arpa/IN: dump failed:
> permission
> > denied
> > Jun 20 10:37:21 bonsai named[5196]: dumping master
> > file: tmp-XXXXJzlECI: open: permission denied
> > Jun 20 10:37:21 bonsai named[5196]: zone
> mylan.lan/IN:
> > dump failed: permission denied
> 
> Check whether you are running bind in chrooted
> setup. If so be sure all
> files - zone files and named.conf - are inside the
> chroot environment,
> which is by default /var/named/chroot/. Check your
> settings in the
> named.conf, especially the instructions where bind
> shall find the zone
> files.
> 
> Alexander
> 

I'm not running in chroot. Do I need to specify
absolute paths for the zone files?
Didn't have to in FC1, so I don't know what has
changed.
Thanks,


	
		
__________________________________
Do you Yahoo!?
New and Improved Yahoo! Mail - 100MB free storage!
http://promotions.yahoo.com/new_mail 



[Index of Archives]     [Current Fedora Users]     [Fedora Desktop]     [Fedora SELinux]     [Yosemite News]     [Yosemite Photos]     [KDE Users]     [Fedora Tools]     [Fedora Docs]

  Powered by Linux