named error: not listening on any interfaces: Problem solved!)
barmar at bbnplanet.com
Mon Mar 13 20:06:44 UTC 2000
In article <18.104.22.168.20000313135820.007d24a0 at mail.9netave.net>,
<chris at tourneyland.com> wrote:
>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.
The "Permission denied" error messages should have given you the hint that
it was a problem of privileges.
> - 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: bind(dfd=20, [22.214.171.124].53):
>>>> Mar 13 12:33:21 hoss named: deleting interface [126.96.36.199].53
>>>> Mar 13 12:33:21 hoss named: bind(dfd=20, [127.0.0.1].53):
>>>> Mar 13 12:33:21 hoss named: deleting interface [127.0.0.1].53
>>>> Mar 13 12:33:21 hoss named: 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!
Barry Margolin, barmar at bbnplanet.com
GTE Internetworking, Powered by BBN, 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