The dnsmasq initscript fails to disable itself when the dnsmasq package is removed
Bug #1315741 reported by
Josh Hill
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
dnsmasq (Debian) |
Fix Released
|
Unknown
|
|||
dnsmasq (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
I upgraded from 12.04 to 14.04 and found that I had no DNS. After a little searching I noticed that dnsmasq, as started by Network Manager, was listening on 127.0.1.1, yet /etc/resolv.conf was being auto-populated with 127.0.0.1, so DNS lookups were failing.
Manually adding 127.0.1.1 to /etc/resolv.conf lets DNS work until the network state changes, then it gets overwritten again with 127.0.0.1.
I've worked around the issue by adding "nameserver 127.0.1.1" to /etc/resolvconf
Changed in dnsmasq (Debian): | |
importance: | Undecided → Unknown |
status: | New → Unknown |
Changed in dnsmasq (Debian): | |
status: | Unknown → New |
Changed in dnsmasq (Debian): | |
status: | New → Fix Released |
To post a comment you must log in.
Can you find the "nameserver 127.0.0.1" line in one of the files in /etc/resolvconf /resolv. conf.d/ or /run/resolvconf /interface ?