On Thu, 2005-10-27 at 13:12 -0400, [EMAIL PROTECTED] wrote: > I have a problem with bind when I run netstat -a | grep rndc I get > > localhost.localdom:rndc *:* > > I would like to see > > *.rndc > > i do not what to see the localhost stuff
And yet "the localhost stuff" is the truth about where rndc is listening. named should only be listening for rndc on the local interface for security reasons. There is not really a reason to be able to access bind via rndc remotely in most circumstances. If netstat reported that named was accepting connections on *.*:rndc, that might be considered a security hole. Is the problem that you don't want to _see_ that named is listening on the localhost interface or that you don't want named to be _listening_ on the localhost interface? -- Andy Bakun <[EMAIL PROTECTED]> _______________________________________________ tsl-discuss mailing list [email protected] http://lists.trustix.org/mailman/listinfo/tsl-discuss
