RE: FC3 core over RH9, now no BIND - UPDATE

From: Darryl Jones (darryl_at_spyproductions.com)
Date: 06/30/05

  • Next message: Tim Holmes: "Samba on FC3" 
    To: "'For users of Fedora Core releases'" <fedora-list@redhat.com>
Date: Thu, 30 Jun 2005 11:41:35 -0400

    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.

    Ideas?

    Thanks

    Darryl Jones
    System Administrator
    SpyProductions
    Achieve Web Success
    http://spyproductions.com

    > -----Original Message-----
    > From: fedora-list-bounces@redhat.com
    > [mailto:fedora-list-bounces@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
    > replaced
    > > > 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
    >
    >
    > --
    > 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
    > 

    -- 
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: http://www.redhat.com/mailman/listinfo/fedora-list
  • Next message: Tim Holmes: "Samba on FC3"

    Relevant Pages

    • Re: The fedora 4 SOA slave expired
      ... > In the Fedora 4, the salve fails to contact the master name server if ... I can only guess that you're talking about the BIND DNS server on ... Or, if you're using another name server daemon, its ...
      (Fedora)
    • Re: DNS Server
      ... >> quick reference how to setup DNS server on Fedora? ... Be aware that installing all bind packages of FC will cause bind to be ... Fedora GNU/Linux Core 1 on Athlon CPU kernel 2.4.22-1.2188.nptl ...
      (Fedora)
    • Re: bind9 / chroot
      ... > you actually run bind then, just via the regular init.d script? ... > preconfigured and knows it has to run in a chroot? ... Doesn't Fedora come with a package for running bind chrooted? ...
      (Fedora)
    • Re: Fedora Core 4 Update: caching-nameserver-7.3-4.FC4
      ... > Fedora Update Notification ... The configuration files for setting up a caching name server. ... > will make BIND, the DNS name server, act as a simple caching nameserver. ...
      (Fedora)
    • Re: Use stLinkCriteria for 3 fields
      ... Tips for Access users - http://allenbrowne.com/tips.html ... can only get it to bind to 1 column; I need it to bind to all 3 columns. ... meaningful or visible to the user), and use it as the bound column of ... John W. Vinson ...
      (microsoft.public.access.forms)