Hi,
the latest version of nsd still needs named-xfer from bind. But recent versions of bind don't include that and I shrink from installing an old version of named.
What do others do in this case?
Arnt
Arnt Gulbrandsen wrote:
Hi,
the latest version of nsd still needs named-xfer from bind. But recent versions of bind don't include that and I shrink from installing an old version of named.
What do others do in this case?
Right now you'll need to use a copy of bind 8. We're working on a replacement of named-xfer that will be part of the next NSD release.
Erik
[On 10 Nov, @ 16:08, Arnt wrote in "named-xfer... ..."]
Hi,
the latest version of nsd still needs named-xfer from bind. But recent
versions of bind don't include that and I shrink from installing an old
version of named.What do others do in this case?
I know the debian package of NSD just pulled the named-xfer in from
bind8 and renamed it nsd-xfer. If you really need axfr you will prob.
still need the bind8's named-xfer.
Another possibility is using a different way of sharing the zone info,
ftp, rsync, etc.
grtz Miek
You can download copy of .deb package and unpack it using *ar* and copy
nsd-xfer out of it. That would be simpler than compiling bind on your
own. .deb is available for almost any platform you can imagine :-).
And you need to do it only once (in case that there will be no security
bugs in named-xfer).
O.
[Quoting Arnt Gulbrandsen, on Nov 10, 16:13, in "named-xfer... ..."]
the latest version of nsd still needs named-xfer from bind. But recent
versions of bind don't include that and I shrink from installing an old
version of named.What do others do in this case?
- Get the latest BIND-8
- unpack it
- cd <unpack-dir>/bind-<version>/src
- make
- cd bin/named-xfer
- become superuser
- make install
Alternatively for the last step: just cp named-xfer to
where you need it.
Regards,
-- ted
PS. We are working on our own named-xfer