If named is not running or is being restarted, a lot of
Dominium operations will fail. This should be handled
more gracefully. For example, if named is being
restarted (perhaps because of a named.conf change),
Dominium could wait a reasonable amount of time for
restart. If named is actually down, an error message
should be returned to the user.
Logged In: YES
user_id=156509
I've changed the restartnameserver script to use "rndc
reload" instead of actually restarting bind. This should
help minimize the likelyness of running into the above
situation.