Has anyone else seen where security updates to Ubuntu 10.04 break resolvconf to the point where resolv.conf is empty after booting? After some research as to why the server suddenly thought the mail server had no MX record and nothing else was responding to ssh - I found this empty file...
So I put the correct info into the file, even though it warns that it will be overwritten, then put the same info into the 'base' file in the resolvconf folder structure.
Seems to have worked. Will have to watch it for the next reboot.
[link][2 comments]