Nicolai: I'm glad I asked because my first thought was that you might have the "dnsmasq" package installed and disabled in a non-standard way. The "dnsmasq" initscript sends "nameserver 127.0.0.1" to resolvconf unless the dnsmasq service is disabled in a standard way. But you don't have the "dnsmasq" package which contains the aforementioned initscript, so this can't be the problem.
We need to find out where that "nameserver 127.0.0.1" line is coming from. It shouldn't be there if you have no caching/forwarding nameserver running. Please install resolvconf, reboot, confirm that you have resurrected the problem and send the output of: ls -l /etc/resolv.conf lsattr /etc/resolv.conf ls -l /run/resolvconf ls -l /run/resolvconf/interface for F in /run/resolvconf/interface/* ; do echo "=== $F ===" ; cat "$F" ; done for F in /etc/resolvconf/resolv.conf.d/* ; do echo "=== $F ===" ; cat "$F" ; done -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1001881 Title: "nameserver 127.0.0.1" in resolv.conf causes failure of name resolution To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/1001881/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
