[BlueOnyx:18814] Re: BlueOnyx server down

[Tom]

Hi Michael,

> 5209R:
> 
> systemct restart named-chroot
> 
> On both then check with "tail -200 /var/log/messages" what error
> messages (if any) you got that are related to either "bind" or "named"
> in the log.
> 
OK I found why it wasn't working. The "l" was missing. 
So here is the results from running systemctl start named.service:

Job for named.service failed because the control process exited with error 
code. See "systemctl status named.service" and "journalctl -xe" for 
details.