> > <wild speculation>
> > A /etc/rndc.conf file seems to be made by the 9.1.0-1mdk package, but
> > doesn't this file contain a crypto string that should be unique to the
> > host? If all the mandrake hosts which are running named have the same
> > /etc/rndc.conf file, does this pose a security risk for these hosts?
> > </wild speculation>
> No I inst all the defalut sample one ..
I'll go through the docs soon to doublecheck... Anyway, redhat is doing
the same in rawhide at the moment...
> > When I try to start named on my box the following shows up in
> > /var/log/syslog:
> >
> > Jan 20 10:43:33 d10179 named[8868]: starting BIND 9.1.0 -u named
> > Jan 20 10:43:33 d10179 named[8868]: using 1 CPU
> > Jan 20 10:43:33 d10179 named: named startup succeeded
> > Jan 20 10:43:33 d10179 named[8872]: loading configuration from
> > '/etc/named.conf'
> > Jan 20 10:43:33 d10179 named[8872]: the default for the 'auth-nxdomain'
> > option i
> > s now 'no'
> > Jan 20 10:43:33 d10179 named[8872]: no IPv6 interfaces found
> > Jan 20 10:43:33 d10179 named[8872]: listening on IPv4 interface lo,
> > 127.0.0.1#53
> > Jan 20 10:43:33 d10179 named[8872]: listening on IPv4 interface eth0,
> > 213.46.10.
> > 179#53
> > Jan 20 10:43:33 d10179 named[8872]: listening on IPv4 interface eth1,
> > 192.168.1.
> > 254#53
> > Jan 20 10:43:33 d10179 named[8872]: couldn't open pid file
> > '/var/lib/run/named.p
> > id': No such file or directory
> > Jan 20 10:43:33 d10179 named[8872]: exiting (due to early fatal error)
> >
> > I think this is quite similar to the xfs problem we had a while back...
> >
> > (on RedHat's rawhide bind package I noticed that they have a patch
> > named: bind-9.1.0b1-varrun.patch).
> Yep, looks like we need to apply this patch.
;-) Geoff: You do it?
Stefan
