From: Christopher Chan Sent: November 25, 2009 15:50
> >> Also in the steps you have taken above you are stopping bind
> >> via rndc stop and then trying to start it with the unknown
> >> "start" command. Even if "start" was known it would not work,
> >> rndc communicated directly with named, and since it was already
> >> stopped in a previous step there is no way that your "start"
> >> (or any other command, reload, flush, whatever) could work at
> >> that point.
> >
> > That would explain a lot but it would have been more useful if the
> > rndc command had returned an error saying something like "start
> > command unknown" rather than accepting the command and indicating
> > a communication problem.
>
> So file a bug with the BIND developers about this rather obvious
> 'bug'.
Good suggestion and I have done so.
hec
--
Hugh E Cruickshank, Forward Software, www.forward-software.com
_______________________________________________
CentOS mailing list
CentOS@xxxxxxxxxx
http://lists.centos.org/mailman/listinfo/centos
