named error: not listening on any interfaces: Problem solved!)

chris at tourneyland.com chris at tourneyland.com
Mon Mar 13 19:58:20 UTC 2000


ARRG! Right you are. I mistakenly ran named as chris, and not root. On BOTH
machines!!! I thought I killed them because running ps -x | grep named from
root was coming up empty - I didn't realize it wasn't showing me things I
started up as chris. But I switched to chris, and they were there.

Thanks Ralf, and to everyone who helped on this and my previous question.
This has got to be the fastest, most helpful list I've ever seen.

 - Chris

>At 08:31 PM 3/13/00 +0100, you wrote:
>>On Mon, Mar 13, 2000 at 01:15:51PM -0600, chris at tourneyland.com wrote:
>>
>>> Mar 13 12:33:21 hoss named[4639]: bind(dfd=20, [216.62.177.2].53):
Permission denied
>>> Mar 13 12:33:21 hoss named[4639]: deleting interface [216.62.177.2].53
>>> Mar 13 12:33:21 hoss named[4639]: bind(dfd=20, [127.0.0.1].53):
Permission denied
>>> Mar 13 12:33:21 hoss named[4639]: deleting interface [127.0.0.1].53
>>> Mar 13 12:33:21 hoss named[4639]: not listening on any interfaces
>>
>>Hmm, it looks like bind to port 53 fails.
>>Are you sure you trying this as root? If not, kill and restart named! 
>>Is there another named process running? Kill it!
>>
>>
>>
>>
>>




More information about the bind-users mailing list