[Expired for bind9 (Ubuntu) because there has been no activity for 60
days.]
** Changed in: bind9 (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1871183
T
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
Thank you for taking the time to file a bug report.
>From the bind9 versions you mentioned I assume you are using Ubuntu 16.04
(Xenial), could you please add some extra info like you kernel version and
if you have any custom config file that might has impact in this scenario?
I set up an Ubuntu Xe
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
