> -----Original Message----- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On > Behalf Of Jeremy C. Reed > Sent: Wednesday, August 06, 2008 1:08 PM > To: Doug Niven > Cc: bind-users@isc.org > Subject: Re: BIND 9.5.0-P2 & minor rndc errors > > On Wed, 6 Aug 2008, Doug Niven wrote: > > > % rndc refresh > > rndc: 'refresh' failed: unexpected end of input > > It expects at least one more argument (the zone name): > > refresh zone [class [view]] > > > % rndc stop > > > > % rndc start > > rndc: connect failed: 127.0.0.1#953: connection refused > > No "start" command. rndc doesn't start named. rndc sends commands to > named, but since you stopped named it can't connect.
Right... Not sure about Solaris (I'm sure someone else knowledgeable will chime in), but normally it's easiest to start using the appropriate rc script for your OS and passing it the start command such as "/etc/rc.d/named start" on FreeBSD or I think "/etc/init.d/bind9 start" on Debian Linux... You get the idea. This will make sure it starts in the same way as when the system boots using the same startup flags you may have specified... without having to pass them all manually to named. -Vinny
