I can't reproduce n-m updating resolv.conf with 127.0.0.1 by just moving
/usr/sbin/dnsmasq to /usr/sbin/dnsmasq.orig; NM does notice that dnsmasq
can't be started, and updates resolv.conf with the correct DNS
information.
Did you use a different process for testing this, such as having another
process listening on port 53 ?
** Changed in: network-manager (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/930367
Title:
do not run resolvconf when dnsmasq fails to start
Status in “network-manager” package in Ubuntu:
Incomplete
Bug description:
If dnsmasq fails to launch (becuase the binary is missing, say, due
to an overly agressive admin), then network manager should not run
resolvconf to point at the non-running dnsmasq, since that results in
not being able to resolve names.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/930367/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : [email protected]
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
