*** This bug is a duplicate of bug 1042275 ***
https://bugs.launchpad.net/bugs/1042275
** Tags removed: needs-upstream-report
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to dnsmasq in Ubuntu.
https://bugs.launchpad.net/b
*** This bug is a duplicate of bug 1042275 ***
https://bugs.launchpad.net/bugs/1042275
On 06/10/15 11:08, Alkis Georgopoulos wrote:
> Hi Robie,
>
> while this also happens in Debian, the use case is more common in Ubuntu,
> because NetworkManager is patched to use a spawned dnsmasq instance
*** This bug is a duplicate of bug 1042275 ***
https://bugs.launchpad.net/bugs/1042275
Thanks Alkis. I didn't realise that Simon is the Debian maintainer. I
just wanted to try and make sure this bug doesn't languish because it
hasn't gone to the right place.
I'm quite happy for this bug to re
*** This bug is a duplicate of bug 1042275 ***
https://bugs.launchpad.net/bugs/1042275
** This bug has been marked a duplicate of bug 1042275
Please enhance dnsmasq to talk directly to resolvconf and to register only
its actual listening address(es)
--
You received this bug notification
Hi Robie,
while this also happens in Debian, the use case is more common in Ubuntu,
because NetworkManager is patched to use a spawned dnsmasq instance as a local
resolver, and mixing the two DNS servers is problematic (neither bind-dynamic
nor bind-interfaces work very well).
In Debian they mo
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
This sounds like a valid bug for a relatively uncommon use case. Does
this bug affect Debian also? In that case, it would be appropriate to
seek a fix there.
** Summary changed:
- Don't put 127.0.0.1 in resolvcon
6 matches
Mail list logo