** Changed in: lxc (Ubuntu)
Status: Triaged => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1240757
Title:
Bridge not created if bind9 is on
Status in bind
Marking this won't fix for LXD since LXD is now letting API users create
bridges dynamically which makes generating .d files very impractical for
us. We may however be able to add a check for this issue and at least
report a better error to the user.
For LXC, we could still use a .d mechanism sinc
** Changed in: lxd (Ubuntu)
Status: Confirmed => Triaged
** Changed in: lxc (Ubuntu)
Status: Confirmed => Triaged
** Changed in: bind9 (Ubuntu)
Status: Confirmed => Triaged
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which
** Changed in: bind9 (Ubuntu)
Milestone: None => xenial-updates
** Changed in: bind9 (Ubuntu)
Assignee: (unassigned) => LaMont Jones (lamont)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc in Ubuntu.
https://bug
** Also affects: lxd (Ubuntu)
Importance: Undecided
Status: New
** Changed in: lxd (Ubuntu)
Status: New => Confirmed
** Changed in: lxd (Ubuntu)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, wh
Having bind use .d mechanism seems like the cleanest way to handle this.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1240757
Title:
Bridge not created if bind9 is on
Statu
Unfortunately this isn't something that LXC itself can do, unless there
is some kind of .d mechanism where we can dump a bind config snippet
into.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc in Ubuntu.
https://bugs.lau
Yes, I can confirm that the proper setting for ipv4 is:
listen-on { ! 10.0.3.1; any; };
Now, the problem at hands appears again with ipv6. In /var/log/upstart
/lxc-net.log:
dnsmasq: failed to create listening socket for%lxcbr0: Address already in use.
Deactivating ipv6 in bind solves it
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
Touch seeded packages, which is subscribed to lxc in
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
** Tags added: landscape
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1240757
Title:
Bridge not created if bind9 is on
Status in bind9 package in Ubuntu:
Confirmed
Status
Does bind9 yet support named.conf.d ?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1240757
Title:
Bridge not created if bind9 is on
Status in bind9 package in Ubuntu:
Con
It would be ideal if we could create a /etc/named.conf.d/lxc file and
put the "listen-on { ! 10.0.3.1; };" there.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1240757
Title:
This bug just hit me in Ubuntu 14.04 LTS and is quite serious because
LTS is used in servers, and it is common to try to have virtualization
(LXC) as well as being configured as DNS servers (bind9).
Additionally, under some configurations at least, the whole DNS
resolving becomes malfunctioning as
15 matches
Mail list logo
