Comment 3 for bug 689115

Serge,

Thank you for your reply. While I did find that error message, I didn't
know why I would need to change the file and why it wasn't
programmatic-ally handled during the upgrade. I did a 'cat' of the
file which showed how it was created:

root@WebEntU2:/home/evweber# cat /etc/resolv.conf
# Generated by NetworkManager
nameserver 10.110.0.15

If the NetworkManager applet creates this file as a file instead of as a
symbolic link like Bind9 needs it would seem that one of them is in
error.

Please advise.

- Ed

On Thu, 2010-12-16 at 16:23 +0000, Serge Hallyn wrote:

> Thanks for reporting this bug and helping to make ubuntu better.
>
> The logs show that bind9 failed to start because /etc/resolv.conf was not a
> symbolic link. Depending on where the file came from, could you try renaming
> your existing one
>
> mv /etc/resolv.conf /etc/resolv.conf.orig
>
> and then re-try restarting bind9?
>
> ** Changed in: bind9 (Ubuntu)
> Status: New => Invalid
>
> ** Changed in: bind9 (Ubuntu)
> Status: Invalid => Incomplete
>