When this message happens name service times out.

[Cinense, Mark]

Mark,

	Would you know if there is a way to fix this, or prevent my
nameservice from hanging.  Also I found this in my log as well.

May  9 07:04:40 ns4 named[22432]: There may be a name server already running
on [127.0.0.1].53
May  9 07:04:40 ns4 named[22432]: There may be a name server already running
on [127.0.0.1].53
May  9 07:04:40 ns4 named[22432]: deleting interface [127.0.0.1].53
May  9 07:06:40 ns4 named[22432]: There may be a name server already running
on [134.253.16.5].53
May  9 07:06:40 ns4 named[22432]: There may be a name server already running
on [134.253.16.5].53
May  9 07:06:40 ns4 named[22432]: deleting interface [134.253.16.5].53
May  9 07:06:40 ns4 named[22432]: not listening on any interfaces

	Looks as if named caught itself loading another daemon, and then
hanging itself.  We have a script that monitors the system to see if named
is running, if not, the script then reloads the name daemon.  Is there
something in BIND that does this so I can replace it in place of the script?

Mark A Cinense

		-----Original Message-----
		From:	Mark.Andrews at nominum.com
[mailto:Mark.Andrews at nominum.com]
		Sent:	May 09, 2000 6:51 PM
		To:	Cinense, Mark
		Cc:	'Bind-Users-Group'
		Subject:	Re: When this message happens name service
times out. 


			Apart from the other causes there is an additional
cause. If
			you have set "query-source * port 53;" in options,
queries
			directed at interfaces that were not up when named
started /
			last scanned the interface table will end up on the
query
			socket and not a listening socket.

			Mark

		> Greetings all,
		> 
		> 	About a month ago we upgraded our 10mb NIC to a
100mb NIC on a SPARC
		> 5 270mhz with 96mb of memory.  Our environment is about
8500 + machines,
		> that includes the servers.  I have a script that runs
daily via cron, and
		> its job is to gather statistics on the nameserver.  This
script also
		> restarts named by getting the named.pid info, and doing a
kill -ILL on that
		> pid.  Well after the upgrade of the NIC's, I am now
getting this message in
		> my message log.
		> 
		> May  9 07:50:20 ns4 named[22455]: refused query on
non-query socket from
		> [134.253.93.44].2072
		> May  9 07:50:20 ns4 named[22455]: refused query on
non-query socket from
		> [134.253.22.3].53
		> 
		> 	So what I did is change the schedule to every other
day instead of
		> everyday.  Unfortunately this only fixed this for a week.
Today it happened
		> again.  Has anyone seen this error message?  This is
killing my uptime, and
		> I am wondering if we need new machines.  By the way the
cpu utilization
		> looks like this through top.
		> 
		> CPU states: 92.7% idle,  3.4% user,  4.0% kernel,  0.0%
iowait,  0.0% swap
		> Memory: 96M real, 10M free, 62M swap free
		> 
		>      PID  USERNAME    THR  PRI   NICE  SIZE         RES
STATE   TIME    CPU
		> COMMAND
		> 22455    root                    1    58          0
11M     9400K
		> sleep     14:05  3.85%     named
		> 
		> thanks for any Reponses,
		> 
		> Mark A Cinense
		> 
		> 
		> 
		--
		Mark Andrews, Nominum Inc.
		1 Seymour St., Dundas Valley, NSW 2117, Australia
		PHONE: +61 2 9871 4742                 INTERNET:
Mark.Andrews at nominum.com