Please don't enable the NetworkManager-controlled dnsmasq by default
Bug #1086693 reported by
Ryan Farmer
This bug affects 2 people
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| network-manager (Ubuntu) |
Confirmed
|
Undecided
|
Unassigned | ||
Bug Description
In Ubuntu's default configuration, NetworkManager spawns a copy of dnsmasq, which breaks DNS lookups for me. It has done this since Ubuntu 12.04, when this was made the default. I've just been following the workaround that has worked for other people of disabling dnsmasq in /etc/NetworkMan
There have been multiple bug reports about the various problems of this configuration, but it remains the default configuration in 12.10, and breaks my DNS lookups there, as well.
Someone mentioned I should file a bug. So, why not? It'll just be ignored like they always are, but fine. You got it!
Revision history for this message
| Ryan Farmer (ryanfarmer-t) wrote | #1 |
Revision history for this message
| Ryan Farmer (ryanfarmer-t) wrote | #2 |
Revision history for this message
| Thomas Hood (jdthood) wrote | #3 |
| summary: |
- DNS lookup fails intermittently with Comcast, when Network Manager's - copy of dnsmasq is in use. + Please don't enable the NetworkManager-controlled dnsmasq by default |
| description: | updated |
Revision history for this message
| Launchpad Janitor (janitor) wrote | #4 |
| Changed in network-manager (Ubuntu): | |
| status: | New → Confirmed |
Revision history for this message
| Nick Craig-Wood (nick-craig-wood) wrote | #5 |
Revision history for this message
| Ryan Farmer (ryanfarmer-t) wrote | #6 |
To post a comment you must log in.
There are really two issues here. One is that nm-dnsmasq isn't working properly for you. The second is that you'd like it not to be enabled by default.
Let's consider this report (bug #1086693) to be your request that nm-dnsmasq not be enabled by default.
Please take a look at the reports that have already been filed against the dnsmasq package, especially bug #1003842. If you feel that your bug is different, file a new report against dnsmasq. These reports are not ignored!