bind 8.2.2p7 dies

Lyle Lyle at lcrcomputer.com
Tue Mar 13 23:09:16 UTC 2001


Attached are a portion of the logs for my name server here.  What is
happening is that it stops responding.  I am going to try to make & install
9.1.1rc4.  This is a LM 6.0 Linux server, that is also running Apache(if
that matters).  But I see tons of lame server messages mainly from
'Ameritech.net'.  I already have 9.1.1rc4 running on a slave server under RH
6.2 linux and it seems to be fine.

I wrote a short perl script to check DNS by running dig against the
localhost and see if it responds.  If it doesn't restart named.  I run this
every 15 minutes.  I have three DNS servers, 2 running redhat 6.2 and this
LM Linux 6.0 server.  The LM 6.0 Linux server is the only server that stops
responding from time to time.  At 15.32, apparently named stopped responding
and my perl script restarted.

So I guess, my question to the list is, is it named 8.2.2p7 or LM 6.0 that
is at the bottom of these named problems? Or am I wasting my time to update
to Bind 9.1.1rc4?

Thanks,
Lyle

Portion of the messages log from the 'problem server'.

Mar 13 15:15:47 linux named[354]: Lame server on '78.92.109.64.in-addr.arpa'
(in '109.64.in-addr.arpa'?): [207.231.134.27].53 'NS2.AMERITECH.NET'
Mar 13 15:15:47 linux named[354]: Lame server on '78.92.109.64.in-addr.arpa'
(in '109.64.in-addr.arpa'?): [206.141.251.2].53 'NS1.AMERITECH.NET'
Mar 13 15:25:49 linux named[354]: Lame server on '78.92.109.64.in-addr.arpa'
(in '109.64.in-addr.arpa'?): [206.141.251.2].53 'NS1.AMERITECH.NET'
Mar 13 15:25:49 linux named[354]: Lame server on '78.92.109.64.in-addr.arpa'
(in '109.64.in-addr.arpa'?): [207.231.134.27].53 'NS2.AMERITECH.NET'
Mar 13 15:32:01 linux named: named shutdown succeeded
Mar 13 15:32:02 linux named[1448]: starting.  named 8.2.2-P7 Fri Nov 10
22:43:34 CET 2000
^Iroot at kenobi2.mandrakesoft.com:/usr/src/RPM/BUILD/bind-8.2.2P7/src/bin/name
d

---------Normal startup messages for a slave zone server -----------------

Mar 13 15:32:03 linux named: named startup succeeded
Mar 13 15:35:56 linux named[1449]: Lame server on
'78.92.109.64.in-addr.arpa' (in '109.64.in-addr.arpa'?): [206.141.251.2].53
'NS1.AMERITECH.NET'
Mar 13 15:35:56 linux named[1449]: Lame server on
'78.92.109.64.in-addr.arpa' (in '109.64.in-addr.arpa'?): [207.231.134.27].53
'NS2.AMERITECH.NET'
Mar 13 15:45:58 linux named[1449]: Lame server on
'78.92.109.64.in-addr.arpa' (in '109.64.in-addr.arpa'?): [207.231.134.27].53
'NS2.AMERITECH.NET'
Mar 13 15:45:59 linux named[1449]: Lame server on
'78.92.109.64.in-addr.arpa' (in '109.64.in-addr.arpa'?): [206.141.251.2].53
'NS1.AMERITECH.NET'
Mar 13 15:56:01 linux named[1449]: Lame server on 'search.ebay.com' (in
'EBAY.com'?): [209.24.149.41].53 'NS1.BEST.COM'
Mar 13 15:59:16 linux named[1449]: Lame server on
'78.92.109.64.in-addr.arpa' (in '109.64.in-addr.arpa'?): [206.141.251.2].53
'NS1.AMERITECH.NET'
Mar 13 15:59:16 linux named[1449]: Lame server on
'78.92.109.64.in-addr.arpa' (in '109.64.in-addr.arpa'?): [207.231.134.27].53
'NS2.AMERITECH.NET'


More information about the bind-users mailing list