Subject: Re: Bind 8.2.2p5 pulled up to -release?
To: Bernd Ernesti <>
From: Frederick Bruckman <>
List: current-users
Date: 11/29/1999 15:14:28
On Sun, 28 Nov 1999, Bernd Ernesti wrote:

> On Sun Nov 28 20:01:07 1999, Jim Wise wrote:
> > On Sun, 28 Nov 1999, Rick Byers wrote:
> > 
> > >Is the new bind code (8.2.2p5) going to be pulled up to the release
> > >branch?  I need the security fixes, so if it's not going to be pulled up
> No one tested it so it isn't requested to be pulled up and I can't test it
> under 1.4.x now.

I'm running named on my ipnat gateway for a couple hosts, all running
netbsd-1-4, so I'll give it a shot.

> > >to the -release branch I'll just install it manually.  IMHO, the security
> > >considerations are severe enough that we want it in 1.4.2 (and as soon as
> > >possible in -release).
> Just try to drop the -current dist/bind and usr.sbin/bind into a 1.4.x system
> and see if it works. I see no reason now why it shouldn't work.

It builds and installs (after "mkdir -p /usr/share/examples/named"),
and everything seems to work, except "ndc" apparently can't fetch the
path to the working named.conf anymore...

  root-> /usr/sbin/named /etc/namedb/named.conf
  root-> ps | grep named
  1352  1136  8405     1     0 ??       /usr/sbin/named /etc/namedb/named.conf 
   496   200  8408  6124     0 ttyp2    grep named 
  root-> named.restart
  can't open '/etc/named.conf' 
  ndc: error: could not start new name server (/usr/sbin/named)
  root-> ps | grep named
   212    92  8416  6124     0 ttyp2    grep named 

"named.restart" works fine in netbsd-1-4.