A few weeks ago, I started to experience this issue again, even if BIND starts after network manager.
root@Chuck:/home/claudio# /etc/init.d/bind9 status [FAIL] bind9 is not running ... failed! root@Chuck:/home/claudio# /etc/init.d/bind9 start [ ok ] Starting domain name service...: bind9. root@Chuck:/home/claudio# /etc/init.d/bind9 status [ ok ] bind9 is running. root@Chuck:/home/claudio# ls /etc/rc2.d/ README S20acpi-support S21bluetooth S24isc-dhcp-server S01motd S20anacron S21cpufrequtils S24kerneloops S01nvidia-kernel S20apmd S21network-manager S24rsync S16rpcbind S20atd S23bind9 S24samba S17nfs-common S20dbus S23cups S25minissdpd S19acpi-fakekey S20lastfmsubmitd S23gdm3 S25rc.local S19binfmt-support S20loadcpufreq S23pulseaudio S25rmnologin S19hostapd S20ntp S23saned S25stop-bootlogd S19rsyslog S20openbsd-inetd S24bootlogs S19sudo S20ssh S24bumblebeed S20acpid S21avahi-daemon S24cron root@Chuck:/home/claudio# head -n 14 /etc/init.d/bind9 #!/bin/sh -e ### BEGIN INIT INFO # Provides: bind9 # Required-Start: $remote_fs # Required-Stop: $remote_fs # Should-Start: $network $syslog network-manager # Should-Stop: $network $syslog # Default-Start: 2 3 4 5 # Default-Stop: 0 1 6 # Short-Description: Start and stop bind9 # Description: bind9 is a Domain Name Server (DNS) # which translates ip addresses to and from internet names ### END INIT INFO If you need any other information, just ask :) Thanks! Claudio
