Hello Thomas, so a little while ago (maybe 3 weeks) there was an update to the resolvconf package, which mysteriously changed /run/resolvconf/resolv.conf to use 127.0.0.1 as the DNS server, along with a correct search domain.
Initially, when I was connecting to a network and specified DHCP for the address, but a manually entered DNS record, the resolv.conf would directly point to the DNS server I specified rather than localhost. The behavior appears to have changed. I'll check on my school network whether this is still an issue, so tomorrow in other words. Incidentally, I should mention that nm-applet is a little wonky. Sometimes it stops updating the list of available APs, and I have to run "killall nm-applet" then run nm-applet for it to work properly. On occasion this happens twice within a single session, but generally every other time I resume my computer after it is suspended. Browsing the internet stops working, my connection to an 802.1x authenticated network won't work, etc until I respawn nm-applet. File a new bug? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1050721 Title: Nameserver address entered for one connection gets added to resolv.conf for all connections To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1050721/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
