RE: Secondary Server

::what errors? On which platform? With bind or with nsd?
::
::I'm running with the named-xfer from bind8, a cronjob runs
::every hour. I works perfect,
::
::grtz Miek
::

My mistake, I should have included that information with my first
message.

I have a box running Slackware 9.1. NSD is set up as a secondary server
and listens on eth0 (wan). Bind-9 is set up for recursive-only and
listens on eth1 and lo (lan). All of that is working flawlessly, thanks
in part to the great people on this list. 8^)

So I want to have my secondary server transfer from the primary, (which
I also control) that is a couple hundred miles away. The docs say that
I need named-xfer, which stopped being released with bind-8 I believe.
I downloaded the source for bind 8.4.4 which includes named-xfer. I got
the main source, the docs, and the contrib packages because I wasn't
sure what I'd need. I untarred the source package and looked through
everything that was extracted. The most obvious choice was the makefile
/src/bin/named-xfer, so I tried to use that. I couldn't find any real
documentation so I tried the most obvious things. Trying ./configure
returns No such file or directory. Make returns the following block. I
don't understand all the references to a directory called freebsd. I
didn't see that the source was specific to any *nix, there was only one
choice.

root@spongebob:/src/bin/named-xfer# ./configure
-bash: ./configure: No such file or directory

root@spongebob:/src/bin/named-xfer# make
cc -I../../port/freebsd/include -I../../include -g -Wall -c
named-xfer.c
In file included from named-xfer.c:170:
../../port/freebsd/include/port_after.h:76:23: port_ipv6.h: No such file
or directory
In file included from named-xfer.c:178:
../named/named.h:58:23: pathnames.h: No such file or directory
named-xfer.c: In function `main':
named-xfer.c:339: `_PATH_DEVNULL' undeclared (first use in this
function)
named-xfer.c:339: (Each undeclared identifier is reported only once
named-xfer.c:339: for each function it appears in.)
named-xfer.c:357: `_PATH_TMPXFER' undeclared (first use in this
function)
named-xfer.c:700: structure has no member named `sa_len'
named-xfer.c:700: structure has no member named `sa_len'
named-xfer.c:700: structure has no member named `sa_len'
named-xfer.c: In function `print_comment':
named-xfer.c:1064: structure has no member named `sa_len'
named-xfer.c:1064: structure has no member named `sa_len'
named-xfer.c:1065: structure has no member named `sa_len'
named-xfer.c: In function `getzone':
named-xfer.c:1154: structure has no member named `sa_len'
named-xfer.c:1173: structure has no member named `sa_len'
named-xfer.c:1176: structure has no member named `sa_len'
named-xfer.c:1186: structure has no member named `sa_len'
named-xfer.c:1198: structure has no member named `sa_len'
named-xfer.c:1203: structure has no member named `sa_len'
named-xfer.c:1203: structure has no member named `sa_len'
named-xfer.c:1204: structure has no member named `sa_len'
named-xfer.c:1652: structure has no member named `sa_len'
named-xfer.c:1662: structure has no member named `sa_len'
named-xfer.c:1662: structure has no member named `sa_len'
named-xfer.c:1938: structure has no member named `sa_len'
named-xfer.c:1947: structure has no member named `sa_len'
named-xfer.c:1947: structure has no member named `sa_len'
named-xfer.c: In function `tsig_key_from_addr':
named-xfer.c:3142: structure has no member named `sa_len'
named-xfer.c:3142: structure has no member named `sa_len'
named-xfer.c:3142: structure has no member named `sa_len'
named-xfer.c:3142: structure has no member named `sa_len'
named-xfer.c:3142: structure has no member named `sa_len'
named-xfer.c:3142: structure has no member named `sa_len'
named-xfer.c:3142: structure has no member named `sa_len'
named-xfer.c:3142: structure has no member named `sa_len'
make: *** [named-xfer.o] Error 1

Once again, thank you for your time
Dave Coursey

[On 05 Feb, @15:09, David wrote in "RE: Secondary Server ..."]

::every hour. I works perfect,
::
::grtz Miek
::

My mistake, I should have included that information with my first
message.

I have a box running Slackware 9.1. NSD is set up as a secondary server

ah :slight_smile: I use Debian, and also had some problems with bind8. Do bind8 and
bind9 bite each other on Slackware? Otherwise the quickest solution would
be to just install the bin package of bind8 from Slackware and tell nsd
to use the named-xfer from that.

root@spongebob:/src/bin/named-xfer# make
cc -I../../port/freebsd/include -I../../include -g -Wall -c

what if you give 'make' in the top level dir of bind8, ie. you want
to compile the whole package? Does that work? On Debian it does...

grtz
      Miek

[Quoting "David Coursey", on Feb 5, 15:12, in "RE: Secondary Server ..."]

root@spongebob:/src/bin/named-xfer# ./configure
-bash: ./configure: No such file or directory

(Did you really install the bind source directly in / or is
your prompt misleading me?).

There is no ./configure, you better run make in bind-8.4.4/src
(which configures and makes everything).
Then go to bin/named-xfer and run make install there to
only install named-xfer.

Regards,
-- ted

::There is no ./configure, you better run make in
::bind-8.4.4/src (which configures and makes everything). Then
::go to bin/named-xfer and run make install there to only
::install named-xfer.

That worked. I didn't know that I had to make the whole thing before
making just named-xfer.
You guys rock!

Dave