bind 8.2.2p5 won't listen on any interface
Mark.Andrews at nominum.com
Mark.Andrews at nominum.com
Fri May 26 00:55:34 UTC 2000
There was most probably a named-xfer still running which was holding
the sockets open.
This is addressed by BIND 8.2.3 (actually BIND 8.2.2-P6 but this
was not generally released).
897. [support] descriptors used by named should not be inherited by
named-xfer.
Mark
> Hi all,
>
> I'm running Red Hat 5.2 on my machine which is an
> IP masquerading (NAT) gateway for my home
> network. I am using bind 8.2.2p5 as a caching-
> only nameserver. My problem is that somewhere
> along the line, named got killed and didn't clean
> up after itself. Here's the relevant part of 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.
>
> Naturally, I checked and there is only one
> instance of named running.
>
> Could somebody please tell me how to recover from
> this condition? I tried waiting for it to clear
> itself, which had worked in the past, but no luck
> this time.
>
> Any assistance would be gratefully appreciated!
>
>
>
> Sent via Deja.com http://www.deja.com/
> Before you buy.
>
>
--
Mark Andrews, Nominum Inc.
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742 INTERNET: Mark.Andrews at nominum.com
More information about the bind-users
mailing list