ndc errors documented?

[Mark.Andrews at nominum.com]

	Are you running chroot?
		use "ndc -c <chroot><rest_of_path> ..."
	Did you log a syntax error in named.conf?
		fix the error the restart or reload using pid mode of ndc
	Did you override the default path with a controls clause?
		use "ndc -c <path> ..."

	Mark

> Are ndc errors documented anywhere (apart from in the code, that is)?  I
> recently had a case where a nameserver was running correctly but attempts
> to use ndc brought up the error:
> 
> ndc: error: ctl_client: evConnect(fd 3): Connection refused
> ndc: error: cannot connect to command channel (/etc/ndc)
> 
> Restarting named by killing the process and running named directly had no
> effect on the above error; killing named and restarting with "ndc restart"
> fixed it.  This is BIND 8.2.2p5 on Solaris; named is normally started by
> calling it directly, not via ndc, and ndc normally works.  Can someone
> tell me what happened in this case?  Thanks.
> 
> Before anyone jumps on me I've looked on the ISC site for documentation
> and at the mailing list archive, at two FAQs, various parts of the DNSRD
> site and Ask Mr.DNS before coming here, honest...
> 
> -- 
> Sam Wilson
> Network Services Division, Computing Services
> The University of Edinburgh
> Edinburgh, Scotland, UK
> 
> 
--
Mark Andrews, Nominum Inc.
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742                 INTERNET: Mark.Andrews at nominum.com