Ubuntu
bind9 package

  1. Bug #689115
  2. Comment #2

Comment 2 for bug 689115

Revision history for this message
Serge Hallyn (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?