An issue I've noticed is that `sudo dpkg-reconfigure resolvconf` doesn't always fix the issue, because, as the program notes, a reboot is sometimes required to actually refresh the cached dns info. This makes using this on a laptop occasionally frustrating when traveling between wifi hotspots or resuming after a suspend, because you either have to manually edit your /etc/resolv.conf or reboot if you don't know your local nameserver IP.
I've gotten in the habit of manually recording the domain/search/nameserver fields of all the networks I typically used, so that if resolvconf locks up, I can quickly fix it. Obviously, I shouldn't need to do this. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1000244 Title: /etc/resolv.conf symlink does not exist after initial installation of resolvconf package To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/1000244/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
