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.
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 main.cf /run/resolv. conf /etc/resolv.conf /run/resolv. conf
$ sudo touch /etc/postfix/
$ sudo rm /etc/resolv.conf
$ sudo ln -s /etc/resolvconf
$ ls -l /etc/resolv.conf
lrwxrwxrwx 1 root root 31 2009-08-16 13:42 /etc/resolv.conf -> /etc/resolvconf
$ sudo reboot
After:
$ ls -l /etc/resolv.conf /run/resolv. conf
lrwxrwxrwx 1 root root 31 2009-08-16 13:42 /etc/resolv.conf -> /etc/resolvconf