Ok attempt #2.
Looks like the original clause below didn't match any addresses so I was
getting connection refused messages
listen-on { ! 10.0.3.1; };
What I found worked on my end was specifying a secondary address match
list 'any' which we fall through to match any ipv4 address that is not
hmm, I should've validated this statement above further on deployments.
I am seeing other errors with bind with the above suggestion. I'll debug
more and present results.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to bind9 in Ubuntu.
Looks like the proper syntax for the listen-on named config is either
Just tested on MAAS dns service which fails > 75% of the time when brought up
in a vm due to timing issues.
The proposed "listen-on { ! 10.0.3.1; };" cannot be parsed by bind
because ! is supposed to be outside the addres
Will need to confirm once we have a 0.94.3-0ubuntu2 available for
deployment
lp:1468335 seems very likely related
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to ceph in Ubuntu.
https://bugs.launchpad.net/bugs/1477225
Title:
ceph-r
** Tags added: landscape
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to mongodb in Ubuntu.
https://bugs.launchpad.net/bugs/1471237
Title:
Mongo causes juju to fail: bad record MAC
To manage notifications about this bug go to:
https
