Comment 4 for bug 807153
Revision history for this message
| Brian Vaughan (bgvaughan) wrote Re: named does not shut down after "service bind9 stop" | #4 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0e1f616
(Get the code!)
This looks like the bug I want to report. I find that shutting down bind9 is erratic: sometimes it succeeds, sometimes not. This is a common result of shutting it down at the command line:
<code>brian@$ sudo service bind9 stop
* Stopping domain name service... bind9
rndc: connect failed: 127.0.0.1#953: connection refused</code>
I need to send a break (usually with CTRL-C) to get past this.
I often have difficulty shutting down or rebooting my system, as it often hangs early in the process; bind9 seems to be among the first services to be shut down, so I suspect it is the root of that problem as well.
I notice that Matthias pointed out that he is using IPv6 and dnssec. I am using an IPv6 tunnel and have configured bind9 for dnssec validation; I had purged and reinstalled bind9 in trying to troubleshoot this problem, and it didn't hang on restarts before I re-enabled dnssec validation. That was only a few restarts; with an intermittent problem, it's hard to be sure. I will try disabling dnssec validation for a few days and see if that helps.