Incorrect error handing of the bind9 app state causes no transition to the inactive state
The GetAppState()
logic returns early when communication with named fails. As a result, the info about the app is not updated in the database. So, for example, the active flag remains true, while it should be put to false. The daemon appears to be online in the UI even though there is no connection to it.