Comment 2 for bug 1782640

This failure is surprising:
Jul 19 07:43:58 juju-f3de6a-1-lxd-3 named[28676]: open: /etc/bind/named.conf: permission denied
Jul 19 07:43:58 juju-f3de6a-1-lxd-3 named[28676]: loading configuration: permission denied

Crashdump doesn't seem to capture those files (it grabs /etc/netplan and /etc/network but not /etc/bind).

There is a warning in the unit log:
2018-07-19 07:43:50 WARNING juju-log cluster:6: Request for sync sent but remote sync time is too old, defering until a more up-to-date target is available

I'm not sure where that is coming from.

We can see the charm writing the files here:
2018-07-19 07:43:58 DEBUG juju-log dns-backend:76: Writing file /etc/bind/named.conf.options root:root 640
2018-07-19 07:43:58 DEBUG worker.uniter.jujuc server.go:181 running hook tool "juju-log"
2018-07-19 07:43:58 DEBUG worker.uniter.jujuc server.go:181 running hook tool "network-get"
2018-07-19 07:43:58 DEBUG worker.uniter.jujuc server.go:181 running hook tool "juju-log"
2018-07-19 07:43:58 DEBUG juju-log dns-backend:76: Writing file /etc/bind/named.conf root:root 640

Those both seem to be happening in 07:43:58. So it seems we just wrote the file, but bind is failing to read it?