bind 8.2.2p5 won't listen on any interface

P_K_Pandita pkpandita at hss.hns.com
Sat May 27 06:56:58 UTC 2000


Hi,
 Pls check whether port 53 is still in use even after killing the
named.Best way to know this is use lsof utility if u have it.It is a
freeware utility.
lsof -l|grep 53
it will show u the process and the port that is being used.Kill the pid
.then restart named.


-P.K.Pandita
Technical Leader (Unix Team)
Hughes Software Systems Ltd.
Plot #31,Sector-18,Electronic City,
Haryana (Gurgaon)-122 015  INDIA
Tel:+91-124-346666 ex:2125


On Sat, 27 May 2000, P_K_Pandita wrote:

> 
> 
> -P.K.Pandita
> Technical Leader (Unix Team)
> Hughes Software Systems Ltd.
> Plot #31,Sector-18,Electronic City,
> Haryana (Gurgaon)-122 015  INDIA
> Tel:+91-124-346666 ex:2125
> 
> 
> On Thu, 25 May 2000 rclocher3 at my-deja.com wrote:
> 
> > 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.
> > 
> > 
> 
> 
> 




More information about the bind-users mailing list