[Expired for libvirt (Ubuntu) because there has been no activity for 60
days.]
** Changed in: libvirt (Ubuntu)
Status: Incomplete = Expired
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
[Expired for lxc (Ubuntu) because there has been no activity for 60
days.]
** Changed in: lxc (Ubuntu)
Status: Incomplete = Expired
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
Stéphane,
given your comments pasted into #12, would you recommend calling this
bug wontfix?
** Changed in: libvirt (Ubuntu)
Status: New = Incomplete
** Changed in: lxc (Ubuntu)
Status: New = Incomplete
--
You received this bug notification because you are a member of Ubuntu
This is an issue in trusty, and affects squid-deb-proxy as well.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1205086
Title:
lxc-net dnsmasq --strict-order breaks dns for lxc
There is concern that removing strict-order would at least double the
dns traffic for most users, and is not the proper fix.
From irc logs (#ubuntu-server, feb 24)
stgraber If the reporter is using a desktop machine, the real fix is to use
NetworkManager which will properly setup dnsmasq to
Reopening because this is still an issue in saucy and lxc.
** Changed in: libvirt (Ubuntu)
Status: Expired = New
** Changed in: lxc (Ubuntu)
Status: Expired = New
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in
@sidnei - apologies, I had missed your response, after which the bug
autoexpired.
Hoping to get a comment from stgraber or cyphermox.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
[Expired for lxc (Ubuntu) because there has been no activity for 60
days.]
** Changed in: lxc (Ubuntu)
Status: Incomplete = Expired
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
[Expired for libvirt (Ubuntu) because there has been no activity for 60
days.]
** Changed in: libvirt (Ubuntu)
Status: Incomplete = Expired
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
Tested on a cloud instance which doesn't have a local dnsmasq, it ended
up with the following config:
$ cat /etc/resolv.conf
# Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
# DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
nameserver 10.88.0.1
Marking incomplete pending info (from submitter or from me) on comment
#2.
** Changed in: libvirt (Ubuntu)
Importance: Undecided = Low
** Changed in: lxc (Ubuntu)
Importance: Undecided = Low
** Changed in: libvirt (Ubuntu)
Status: New = Incomplete
** Changed in: lxc (Ubuntu)
** Also affects: libvirt (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1205086
Title:
lxc-net dnsmasq --strict-order breaks dns
Does removing --strict-order work for your containers in all cases, or
only some of the time? Looking through the dnsmasq manpage,
1. I'd expected --strict-order to mean that if the first nameserver
doesn't know the answer, we try the second one. Apparently it only
falls back if the first one
So really it looks like the dnsmasq-2.47_no_nxdomain_until_end.patch in
dnsmasq source is what - in MY humbe opinion - is what we'd need. Both
for this, and for bug 1003842 and 1163147.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to
Looking more through comments in
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1003842,
it appears to me that the most uncontraversial fix, rather than removing
--strict-order in lxc's dnsmasq, would be for dnsmasq on your host to
have something like:
The vpn server is running a dnsmasq instance with the following
settings:
addn-hosts=/etc/hosts.openvpn-server
addn-hosts=/etc/hosts.openvpn-clients
no-hosts
dns-forward-max=0
no-resolv
In the vpn server configs, it is pushing it's own IP as a dns server:
push dhcp-option DNS 10.88.0.1
push
16 matches
Mail list logo
