Problems with NDC under linux

[andlil at towerrecords.com]

Well, that sounds reasonable enough, but even if I put the controls
statement into my named.conf file, I get the same error.
I think the key is the "invalid argument" bit, but I'm not sure what is
invalid.  Here's my controls statement from my named.conf file:
     controls {
               unix "/var/run/ndc" perm 0600 owner 0 group 0;
     };
All of this should work as far as I know (perm 0600 is valid, there is a
UID 0 and a GID 0 on my system and /var/run should writeable).
Thoughts?

Thanks,
Andrew Lillie
andlil at towerrecords.com



                                                                                                              
                    Jim Reid                                                                                  
                    <jim at rfc1035.        To:     andlil at towerrecords.com                                      
                    com>                 cc:     bind-users at isc.org                                           
                                         Subject:     Re: Problems with NDC under linux                       
                    02/21/00                                                                                  
                    04:46 AM                                                                                  
                                                                                                              
                                                                                                              



>>>>> "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.