Confirming the solution provided by hashstat. The issue were /etc/resolv.conf was being set as a file and not a symlink was being experienced. After adding the dummy postfix conf file the resolv.conf could be set as a symlink and crucially stayed as a symlink after reboot.
Here are the exact steps taken: Before: $ ls -l /etc/resolv.conf -rw-r--r-- 1 root root 30 2009-08-16 13:38 /etc/resolv.conf $ sudo mkdir /etc/postfix $ sudo touch /etc/postfix/main.cf $ sudo rm /etc/resolv.conf $ sudo ln -s /etc/resolvconf/run/resolv.conf /etc/resolv.conf $ ls -l /etc/resolv.conf lrwxrwxrwx 1 root root 31 2009-08-16 13:42 /etc/resolv.conf -> /etc/resolvconf/run/resolv.conf $ sudo reboot After: $ ls -l /etc/resolv.conf lrwxrwxrwx 1 root root 31 2009-08-16 13:42 /etc/resolv.conf -> /etc/resolvconf/run/resolv.conf -- Network Manager 0.7 doesn't use resolvconf to remove nameserver info if it didn't use resolvconf for adding its nameserver info - wipes /etc/resolv.conf link https://bugs.launchpad.net/bugs/324233 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
