bind-8.2.2-p5 not listening on any interfaces

Barry Margolin barmar at genuity.net
Fri May 26 19:06:38 UTC 2000


In article <8gm4k7$9ds$1 at nnrp1.deja.com>,
Rob Locher  <rlocher at corp.darwin.net> wrote:
>Hi all,
>
>I have bind-8.2.2-p5 running on a machine with Red Hat 5.2.  This
>machine is a gateway between my network and the outside world.  The
>gateway is doing IP spoofing (NAT).
>
>I had to reboot the computer, and when it came back named was not
>working as advertised.  Here is the excerpt from the log:
>
>May 24 21:37:56 chicago named[1048]: ctl_server: bind: Address already
>in use
>May 24 21:39:48 chicago named[1048]: There may be a name server already
>running on [127.0.0.1].53
>May 24 21:39:48 chicago named[1048]: deleting interface [127.0.0.1].53
>May 24 21:41:48 chicago named[1048]: There may be a name server already
>running on [192.168.1.254].53
>May 24 21:41:48 chicago named[1048]: deleting interface
>[192.168.1.254].53
>May 24 21:41:48 chicago named[1048]: not listening on any interfaces
>May 24 21:41:48 chicago named[1048]: Forwarding source address is
>[0.0.0.0].53
>May 24 21:41:48 chicago named[1055]: Ready to answer queries.
>
>I verified that there are no other instances of named running.

Well, something is listening on the port and Unix-domain socket that named
wants to use.  I suggest you use "lsof" to find that process and kill it.

-- 
Barry Margolin, barmar at genuity.net
Genuity, Burlington, MA
*** DON'T SEND TECHNICAL QUESTIONS DIRECTLY TO ME, post them to newsgroups.
Please DON'T copy followups to me -- I'll assume it wasn't posted to the group.



More information about the bind-users mailing list