Comment 11 for bug 928524

Indeed, that's the only scenario that'd be a problem, but to workaround that issue, I added a mention of /etc/dnsmasq.d/ in /etc/default/lxc which is where you'd disable lxc's own dnsmasq.

So in theory anyone disabling LXC's own dnsmasq daemon will see the note that they should also update dnsmasq.d

It'd certainly have been better to get that change done pre-release but considering the number of people hitting it, I still think it's worth the risk as an SRU.