> a working nameserver is a core, essential component of a functioning > network. while named is down, *everything* on the network that uses that > nameserver ceases to function correctly.
That's why you should never have only one "nameserver 127.0.0.1" in your /etc/resolv.conf. Configure one or two more remote nameservers and you're done. It's not critical severity - normal or wishlist would be more appropriate. While I agree that it's not very convenient to have bind9 stopped for longer time periods, there are other ways how to prevent this kind of outage. And it's entirely different from f.e. quagga, where restart could mean loss of connectivity at all. Which clearly doesn't happen with bind - you just loose ability to resolv DNS, when you have only one nameserver configured. Ondrej -- Ondřej Surý <ond...@sury.org> http://blog.rfc1925.org/ -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
