Very Computer

Hi,

Well, as the subject says:-) Here are some logs the 1st was when rh5.1
was in operation:-

   UW PICO(tm) 3.4          File: /var/log/messages.old

Sep  6 23:39:11 jilldando chat[256]: send (ATDT0845 079 8668^M)
Sep  6 23:39:11 jilldando chat[256]: expect (CONNECT)
Sep  6 23:39:11 jilldando chat[256]: ^M
Sep  6 23:39:12 jilldando named[287]: starting.  named 4.9.7-REL Tue Jun
30 15:$
Sep  6 23:39:12 jilldando named[287]: cache zone "" loaded (serial 0)
Sep  6 23:39:12 jilldando named[287]: primary zone "0.0.127.in-
addr.arpa" loade$
Sep  6 23:39:12 jilldando named[287]: primary zone "10.in-addr.arpa"
loaded (se$
Sep  6 23:39:12 jilldando named[287]: primary zone "142.173.152.158.in-
addr.arp$
Sep  6 23:39:13 jilldando named[287]: primary zone "worsdall.co.uk"
loaded (ser$
Sep  6 23:39:13 jilldando named[287]: primary zone "shadow" loaded
(serial 1)
Sep  6 23:39:13 jilldando named[287]: primary zone "wizdom" loaded
(serial 1)
Sep  6 23:39:13 jilldando named[287]: primary zone "hinwick" loaded
(serial 1)
Sep  6 23:39:13 jilldando named[287]: primary zone "spartan" loaded
(serial 1)
Sep  6 23:39:13 jilldando named[287]: primary zone "ppmusic" loaded
(serial 1)
Sep  6 23:39:13 jilldando named[287]: primary zone "camad" loaded
(serial 1)
Sep  6 23:39:13 jilldando named[287]: primary zone "radwell" loaded
(serial 1)
Sep  6 23:39:13 jilldando named[287]: primary zone "simon" loaded
(serial 1)
Sep  6 23:39:13 jilldando named[287]: primary zone "medizone.net" loaded
(seria$
Sep  6 23:39:13 jilldando named[287]: primary zone "cheniston.co.uk"
loaded (se$
Sep  6 23:39:13 jilldando named[972]: Forwarding source address is
[0.0.0.0].13$
Sep  6 23:39:13 jilldando named[973]: Ready to answer queries.

Now all I get is:-

Sep 11 00:49:14 jilldando named[972]: starting.  named 8.1.2 Thu Sep 24
02:47:0$
Sep 11 00:49:14 jilldando named[972]: cache zone "" (IN) loaded (serial
0)
Sep 11 00:49:14 jilldando named[972]: master zone "0.0.127.in-addr.arpa"
(IN) l$
Sep 11 00:49:15 jilldando named[972]: listening on [127.0.0.1].53 (lo)
Sep 11 00:49:15 jilldando named[972]: listening on [10.0.1.252].53
(eth0)
Sep 11 00:49:15 jilldando named[972]: Forwarding source address is
[0.0.0.0].13$
Sep 11 00:49:15 jilldando named[973]: Ready to answer queries.
Sep 11 00:49:15 jilldando named[973]: sysquery:
sendto([128.63.2.53].53): Netwo$

Could it be that since rh5.2 it has compiled something different, it
seems not to be reading all my primary files like it once did?

directory                               /var/named
cache           .                       named.ca
primary         0.0.127.in-addr.arpa    named.local
primary         10.in-addr.arpa         10.rev
primary         142.173.152.158.in-addr.arpa    158.152.173.142.rev
primary         worsdall.co.uk          worsdall.co.uk
primary         worsdall.demon.co.uk    worsdall.demon.co.uk
primary         shadow                  shadow
primary         wizdom                  wizdom
primary         hinwick                 hinwick
primary         spartan                 spartan
primary         ppmusic                 ppmusic
primary         camad                   camad
primary         radwell                 radwell
primary         simon                   simon
primary         medizone.net            medizone.net
primary         cheniston.co.uk         cheniston.co.uk

forwarders 158.152.1.43 158.152.1.58
;
; In addition to the "forwarders" clause, you can force your name
; server to never initiate queries of its own, but always ask its
; forwarders only, by enabling the following line:
;
;options forward-only

All the files exist, it's just named ain't even bothering to read them,
what has named.conf got to do with this?

M
--
Mark Worsdall - Oh no, I've run out of underpants :(



Web site Monitoring:-             http://www.shadow.org.uk/SiteSight/

Mark,

Bind now uses named.conf which has a totally new syntax from named.boot. I can't remember
the location of the "converter" utility on RH5.2, but I think it is in the /usr/doc/bind
directory. Look for a filename of 'named-bootconf.pl'
This is a perl script that will take your existing named.boot file (as input) and convert
it to the new format required for named.conf. Worked great for me...

Steve Cowles
SWCowles at gte dot net

your bind is version 8 now, which works slightly differently from bind 4.
instead of the named.boot, it reads the config from named.conf and it has a
different format. there's a converter somewhere which will make your named.boot
into a named.conf, but i can't remember what it's called now.

--
Sig? Oh yeah... here ya go:
^C

writes

Well named.bootconf.pl doesn't work, it just sits there if I execute it.

Should I upgrade using the latest bind from bind themselves (8.2.1)?
Will that work with linux?
--
Mark Worsdall - Oh no, I've run out of underpants :(



Web site Monitoring:-             http://www.shadow.org.uk/SiteSight/

Quote:>Mark,

>Bind now uses named.conf which has a totally new syntax from named.boot. I can't
>remember
>the location of the "converter" utility on RH5.2, but I think it is in the
>/usr/doc/bind
>directory. Look for a filename of 'named-bootconf.pl'
>This is a perl script that will take your existing named.boot file (as input)
>and convert
>it to the new format required for named.conf. Worked great for me...

How long does it take to do its work?

--
Mark Worsdall - Oh no, I've run out of underpants :(



Web site Monitoring:-             http://www.shadow.org.uk/SiteSight/

Mark,

The reason named-bootconf.pl just "sits there" is because you probably did not specify the
input file, like /etc/named.boot!!!! The program is waiting for input... which typically
is specified as a command line argument (like /etc/named.boot) or comes in from a pipe.

try one of the following commands, they all worked on my system (RH60)

named-bootconf.pl /etc/named.boot   >/etc/named.conf

or

named-bootconf.pl </etc/named.boot   >/etc/named.conf

or even...

cat /etc/named.boot | named-bootconf.pl >/etc/named.conf

Steve Cowles

Quote:>Mark,

>The reason named-bootconf.pl just "sits there" is because you probably did not
>specify the
>input file, like /etc/named.boot!!!! The program is waiting for input... which
>typically
>is specified as a command line argument (like /etc/named.boot) or comes in from
>a pipe.

>try one of the following commands, they all worked on my system (RH60)

>named-bootconf.pl /etc/named.boot   >/etc/named.conf

>or

>named-bootconf.pl </etc/named.boot   >/etc/named.conf

>or even...

>cat /etc/named.boot | named-bootconf.pl >/etc/named.conf

Perfect, thanks, this thread can now be dead:-)

--
Mark Worsdall - Oh no, I've run out of underpants :(



Web site Monitoring:-             http://www.shadow.org.uk/SiteSight/