Sorry we've been trying to pin it down further and it seems it might not
actually be bind9 but our particular setup (virtualbox ubuntu 16.04 VM).
We believe it may be time related and have been able to reproduce just
updating NTP. It seems VM boots w/incorrect clock, bind starts, then NTP
updates t
Seems after upgrading via `dist-upgrade` if bind is disabled first,
system is rebooted, then enabled it logs fine. However logging after 1st
reboot seems to cause syslogging from named to stop. Subsequent reboots
seem to log ok.
--
You received this bug notification because you are a member of Ub
** Description changed:
I noticed bind9 stopped logging via syslog after updating bind9:amd64
(1:9.10.3.dfsg.P4-8ubuntu1.14, 1:9.10.3.dfsg.P4-8ubuntu1.15). Restarting
- the process temporarily fixes it, but seems unstable.
+ the process temporarily fixes it, but syslog seems to stop after rebo
Public bug reported:
I noticed bind9 stopped logging via syslog after updating bind9:amd64
(1:9.10.3.dfsg.P4-8ubuntu1.14, 1:9.10.3.dfsg.P4-8ubuntu1.15). Restarting
the process temporarily fixes it, but seems unstable.
** Affects: bind9 (Ubuntu)
Importance: Undecided
Status: New
--
