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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/930367
Title:
do not run resolvconf when dnsmasq fails to start
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/930367/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
