[Bug 1205086] Re: lxc-net dnsmasq --strict-order breaks dns for lxc non-recursive nameserver

[Serge Hallyn]

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 is down altogether?

2. Given the actual behavior of (1), the default (not --strict-oder and
not --all-servers) should just choose a name server at random.  I would
expect it sometimes happens to choose 10.88.0.1, and that if it is up
and says "I dont' know that host", I'd expect fallback to be the SAME as
with --strict-order.  Which means I would have *expected* dnsmasq to try
the next one, but in fact per your findings it should (randomly, half
time time) simply fail to resolve.

-- 
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 non-recursive
  nameserver

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1205086/+subscriptions