is it work or not?

Kevin Darcy kcd at daimlerchrysler.com
Tue Nov 7 01:47:03 UTC 2000


=C3=D6=C1=F8=C7=F5 wrote:

> this is ndc status result
>
> named 8.2.2-P5 Tue Nov  7 07:59:12 KST 2000  root at xxx.xxx.xxx.xxx:/usr/=
local/
> src/bin/named
> number of zones allocated: 64
> debug level: 0
> xfers running: 0
> xfers deferred: 0
> soa queries in progress: 0
> query logging is OFF
> server is DONE priming
> server IS NOT loading its configuration
>
> it tells me not loading its configuration, but named.conf is on /etc/na=
med.conf.

This is just a badly-worded status message. Read it as "server is DONE lo=
ading its configuration" rather than
"server WILL NOT load its configuration".

> below is end-20 lines of /var/log/messages.
>
> Nov  7 09:51:12 jiny named[776]: listening on [127.0.0.1].53 (lo)
> Nov  7 09:51:12 jiny named[776]: listening on [192.168.1.1].53 (eth0)
> Nov  7 09:51:12 jiny named[776]: listening on [210.205.204.183].53 (eth=
1)
> Nov  7 09:51:12 jiny named[776]: Forwarding source address is [0.0.0.0]=
.1029
> Nov  7 09:51:12 jiny named[777]: Ready to answer queries.
> Nov  7 09:53:55 jiny inetd[463]: auth/tcp: bind: Address already in use
>
> address already in use , it say, why?

Note that the last log entry was from "inetd" not "named", and occurred w=
ell after the "Ready to answer
queries" entry which marks the end of the initialization. "bind" in this =
case refers to the bind() library
call, not BIND, the DNS package. See the bind() man page for more details=
 on the library call (in section 3
or perhaps some variant like 3N or 3XN, depending on your system). Appare=
ntly something was already listening
on the "auth" port when inetd tried to listen (i.e. issue a bind() call f=
ollowed by a listen() call) on that
port number. Short of a reboot, you'll most likely get this log entry eve=
ry time you reload or restart inetd,
because there's probably a stuck process which is holding onto that port.


- Kevin





More information about the bind-users mailing list