** Changed in: lxc (Ubuntu)
Status: Triaged => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1240757
Title:
Bridge not created if bind9 is on
To manage notifications about this
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
** 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
Bugs, which is subscribed
** 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
Bugs, which is subscribed to Ubuntu.
** 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
Bugs, which is
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
Server Team, which is subscribed to bind9 in Ubuntu.
https://bugs.launchpad.net/bugs/1240757
Title:
Bridge not created if bind9 is on
To manage
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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1240757
Title:
Bridge not created if bind9 is on
To manage notifications
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
Server Team, which is subscribed to bind9 in Ubuntu.
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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1240757
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
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
** Tags added: landscape
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1240757
Title:
Bridge not created if bind9 is on
To manage notifications about this bug go to:
** Tags added: landscape
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to bind9 in Ubuntu.
https://bugs.launchpad.net/bugs/1240757
Title:
Bridge not created if bind9 is on
To manage notifications about this bug go to:
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
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
Bugs, which is subscribed to 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
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.
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
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
Does bind9 yet support named.conf.d ?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to bind9 in Ubuntu.
https://bugs.launchpad.net/bugs/1240757
Title:
Bridge not created if bind9 is on
To manage notifications about this bug go to:
Does bind9 yet support named.conf.d ?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1240757
Title:
Bridge not created if bind9 is on
To manage notifications about this bug go to:
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
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
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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1240757
Title:
Bridge not created if
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
Server Team, which is subscribed to bind9 in Ubuntu.
https://bugs.launchpad.net/bugs/1240757
Title:
Bridge
Another potential workaround would be to instruct bind9 to not poll to
discover new interfaces (with interface-interval 0;). I have not tested
this.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to bind9 in Ubuntu.
Another potential workaround would be to instruct bind9 to not poll to
discover new interfaces (with interface-interval 0;). I have not tested
this.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Thanks for reporting this bug.
Note that another workaround should be to put 'listen-on { ! 10.0.3.1
};' in the named.conf.
However, when I tried to reproduce this in saucy I could not, so I
wonder if there is something specific in your configuration
customizations which caused this.
Could you
apport information
** Tags added: apport-collected raring
** Description changed:
LXC will not create the lxcbr0 bridge if bind9 is on, as it can not take
the 10.0.3.1 address. If bind9 is stopped, then LXC successfully creates
the bridge.
Expected result: LXC will create the bridge,
Unfortunately that didn't give me as much information as I'd hoped.
Could you please tell us what release you are on, and (after sanitizing
for any private information) the contents of /etc/bind/named* ?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which
** Attachment added: named.conf.local
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1240757/+attachment/3880400/+files/named.conf.local
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to bind9 in Ubuntu.
** Attachment added: named.conf.options
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1240757/+attachment/3880401/+files/named.conf.options
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to bind9 in Ubuntu.
Currently on Raring. I'm adding comments with the respective files
attached:
** Attachment added: named.conf
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1240757/+attachment/3880399/+files/named.conf
--
You received this bug notification because you are a member of Ubuntu
Server Team,
** Attachment added: named.conf.default-zones
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1240757/+attachment/3880402/+files/named.conf.default-zones
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to bind9 in Ubuntu.
I can reproduce this if I add a 'sleep 10' right before the dnsmasq call
in /etc/init/lxc-net.conf, so it appears to be purely timing related.
(in other words, bind will always by default attach to all interfaces as
they come up; it's not anything in your configs)
The question is then just how
Leaving medium prio since there's a manual workaround (using listen-on).
Leaving confirmed in both lxc and bind9, as the best fix may still
include a change to the bind9 package, rather than named.conf.options
changes made by lxc postinst.
--
You received this bug notification because you are a
Thanks for reporting this bug.
Note that another workaround should be to put 'listen-on { ! 10.0.3.1
};' in the named.conf.
However, when I tried to reproduce this in saucy I could not, so I
wonder if there is something specific in your configuration
customizations which caused this.
Could you
apport information
** Tags added: apport-collected raring
** Description changed:
LXC will not create the lxcbr0 bridge if bind9 is on, as it can not take
the 10.0.3.1 address. If bind9 is stopped, then LXC successfully creates
the bridge.
Expected result: LXC will create the bridge,
Unfortunately that didn't give me as much information as I'd hoped.
Could you please tell us what release you are on, and (after sanitizing
for any private information) the contents of /etc/bind/named* ?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Attachment added: named.conf.local
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1240757/+attachment/3880400/+files/named.conf.local
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1240757
** Attachment added: named.conf.options
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1240757/+attachment/3880401/+files/named.conf.options
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Attachment added: named.conf.default-zones
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1240757/+attachment/3880402/+files/named.conf.default-zones
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Currently on Raring. I'm adding comments with the respective files
attached:
** Attachment added: named.conf
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1240757/+attachment/3880399/+files/named.conf
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
I can reproduce this if I add a 'sleep 10' right before the dnsmasq call
in /etc/init/lxc-net.conf, so it appears to be purely timing related.
(in other words, bind will always by default attach to all interfaces as
they come up; it's not anything in your configs)
The question is then just how
Leaving medium prio since there's a manual workaround (using listen-on).
Leaving confirmed in both lxc and bind9, as the best fix may still
include a change to the bind9 package, rather than named.conf.options
changes made by lxc postinst.
--
You received this bug notification because you are a
45 matches
Mail list logo
