Okay, so now I verified that the nameserver was added to resolv.conf. Then I rechecked before disconnecting and noted that the extra resolv.conf entry had disappeared (without changes to network configuration in the meanwhile). nm-tool reported the correct nameserver address still, and it seemed to work through the local proxy (one presumes). So the generated resolv.conf entry seems both unnecessary and possibly transient, though as said, it has persisted beyond disconnecting the Bluetooth PAN at least two times.
Everything working even without the entry indicates that it probably shouldn't be generated at all. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1389798 Title: Using Bluetooth PAN leaves broken resolv.conf To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1389798/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
