Problems with NDC under linux

Jim Reid jim at rfc1035.com
Mon Feb 21 12:46:06 UTC 2000


>>>>> "Andrew" == andlil  <andlil at towerrecords.com> writes:

    Andrew> Hi, I have BIND 8.2.2p5 installed on an Apple Network
    Andrew> Server 700/150 running Yellow Dog Linux (RH based, PPC
    Andrew> linux).  The daemon runs fine when started manually (ie:
    Andrew> "/usr/sbin/named").  But, when trying to use ndc I get
    Andrew> errors.

    Andrew> If I try to use ndc to start named ("/usr/sbin/ndc
    Andrew> start"), I get back the error: "ndc: error: name server
    Andrew> has not started (yet?)".  In the syslog output, I get the
    Andrew> corresponding errors: "named[15621]: unix control
    Andrew> "/var/run/ndc" socket failed: Invalid argument" and
    Andrew> "named[15621]: ctl_server: socket: Invalid argument"
    Andrew> However, named does get started.

    Andrew> If I then try to stop the running named using ndc, I get
    Andrew> back the errors: "ndc: error: ctl_client: socket: Invalid
    Andrew> argument" and "ndc: error: cannot connect to command
    Andrew> channel (/var/run/ndc)".  There are no corresponding
    Andrew> errors logged to syslog.

It looks like you're missing a controls{} statement from named.conf.
I suspect ndc expects that the socket /var/run/ndc will be used to
talk to the name server, but named hasn't been told to create it.
ndc doesn't use syslog which explains why there are no error messages
from it in the system logs.



More information about the bind-users mailing list