after restart DNS and DHCP server dont start automatically

[OldSkul]

Watchdog. DNS Server is being monitored 24x7
Start at boot time. DNS Server will not start at boot time


Both settings are enabled in both cases. What could be wrong?

I have F12 with latest upgrades and of course latest amahi.

[rgmhtt]

There can be any number of things wrong with the DNS and DHCP values that can cause it to fail.

Look in /var/log/messages for BIND and DHCP messages. Having 'strange' IP addresses can cause 'strange' results. Now I do this as a matter of course and am always fidlling with these two...

[cpg]

Well, it would not start if there is an incorrect configuration.

By construction, if you use the Amahi UI to configure settings it should _always_ be a correct configuration (otherwise it's a bug).

[OldSkul]

it did work in the past, i havent changed anything apart constant updates of F12 and amahi. And thats all.

My server has IP 192.168.1.10... Nothing unusual.

All other services starts without any problems.

[rgmhtt]

chkconfig --list will show you the start status.

check /var/log/messages for any error messages.

[OldSkul]

[rgmhtt]

Note that both dhcpd and named are 'off' all the way across.

There are two ways to 'fix' this. The Setup Servers has an option for services to start at boot time.

Or type in the commands:

chkconfig dhcpd on
chkconfig named on

This sets them to start on boot.