FC3 core over RH9, now no BIND - UPDATE
darryl at spyproductions.com
Thu Jun 30 15:41:35 UTC 2005
Ok, I chrooted BIND and now it sees the zone files. The issue I'm having is
that BIND won't start.
I created the user and group "named" and chowned everything under
/var/named/chown/var/named to named:named, and set /dev/null etc but it
doesn't want to start.
Achieve Web Success
> -----Original Message-----
> From: fedora-list-bounces at redhat.com
> [mailto:fedora-list-bounces at redhat.com] On Behalf Of Alexander Dalloz
> Sent: Wednesday, June 29, 2005 10:22 PM
> To: For users of Fedora Core releases
> Subject: Re: FC3 core over RH9, now no BIND :(
> Am Do, den 30.06.2005 schrieb John Summerfied um 4:04:
> > Darryl Jones wrote:
> > > Hi Guys,
> > >
> > > We installed FC3 over RH9 this weekend, and now BIND isn't seeing
> > > the zone files in /var/named. I did a chown named:named
> for all the
> > > files, made sure the path was in named.conf....nothing. I
> > > named.conf with a backup (pre FC) copy, nothing.
> > You should understand that FC is a test-bed. It's probably
> broken when
> > it's installed, it seems certain to break at least once
> before its next
> > release. Worse, it has a short life cycle.
> > John
> Sorry John, one hasn't to do with the other. Or you may had
> the intention to reply in a different thread. Darryl upgraded
> from a non Fedora distribution where no upgrade path is
> supported in any way and he is confronted with a change of
> the default configuration of bind. I don't see why there is
> need to comment that with "FC is a test-bed" and "probably broken".
> Alexander Dalloz | Enger, Germany | GPG http://pgp.mit.edu
> 0xB366A773 legal statement: http://www.uni-x.org/legal.html
> Fedora Core 2 GNU/Linux on Athlon with kernel 2.6.11-1.35_FC2smp
> Serendipity 04:17:14 up 4 days, 11:09, load average: 1.44, 1.34, 0.87
More information about the users