Setting LXC_DOMAIN causes dnsmasq forwarding loop
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
lxc (Ubuntu) |
Fix Released
|
Medium
|
Serge Hallyn |
Bug Description
Setting LXC_DOMAIN=lxc in /etc/default/
Then, adding server=
Unfortunately if the normal dnsmasq requests an MX or AAAA record, or anything else that the LXC dnsmasq doesn't know how to resolve, the latter forwards to the address in /etc/resolv.conf, which is 127.0.0.1 on a system running a normal dnsmasq. And since the normal dnsmasq is listening on 127.0.0.1, and it's configured to forward queries for the .lxc domain right back to the LXC-dnsmasq. Thus the two dnsmasqs bounce the request back and forth ad infinitum.
The solution is to configure the LXC dnsmasq never to forward requests for the .lxc domain by passing the -S /lxc/ command-line argument. This way, the LXC dnsmasq answers queries that it knows about (A records for LXC hosts), but NAKs queries for any other .lxc domain queries.
See the attached patch to /debian/
The attachment "Patch to /debian/ lxc.lxc- net.upstart" seems to be a patch. If it isn't, please remove the "patch" flag from the attachment, remove the "patch" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team.
[This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issues please contact him.]