[Bug 933723] Re: resolvconf creating bogus resolv.conf file

[Steve Langasek]

At the very least, this behavior is awkward because it means installing
bind9 on a machine will immediately break nameservice until it's
configured, even if the admin *knows* that this configuration is needed
and is planning to address it ASAP.

So I think bind9 should probably not inject itself into resolvconf by
default.

I also think the cert lab should probably fix its install tests to not
pull in an unconfigured bind9 server while testing.

** Bug watch added: Debian Bug tracker #483098
   http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=483098

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to bind9 in Ubuntu.
https://bugs.launchpad.net/bugs/933723

Title:
  resolvconf creating bogus resolv.conf file

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bind9/+bug/933723/+subscriptions