Named has been working fine for months on Fedora core 14 with updates current.

a few days ago it stopped working. I tried a service named restart and received the error message:

stopping named: umount: /var/named/chroot/var/named: device is busy

I tried using kill process, which did not work. However if I use kill 9 <named process>, followed by service named stop, I can then restart the service and it works for a number of hours (less than a day), then stops again and produces the error message above when I try to restart it.

I can get it working again using the procedure above, but only temporarily.

Anyone have any ideas what might fix this issue permanently?

Thanks
switcher

Have you checked the logs at the time the process stops working?

The issue here is why does it stop working, more than why can you not restart it.

I would check /var/log/messages and the bind log file to see if there are any errors causing named to stop.

Also check your disk space.

Thanks for the response and suggestions.

I have attached some samples of named errors found in messages log. Also, I have many gigs of spare disk space on all mounted drives.

Mar 21 11:29:56 server-fedora named[15483]: error (no valid RRSIG) resolving 'cachefly.net/DS/IN': 205.152.144.23#53
Mar 21 11:30:13 server-fedora named[15483]: error (no valid RRSIG) resolving 'linuxquestions.org/DS/IN': 205.152.37.23#53
Mar 21 11:30:13 server-fedora named[15483]: error (no valid RRSIG) resolving 'linuxquestions.org/DS/IN': 205.152.144.23#53
Mar 21 11:30:13 server-fedora named[15483]: error (network unreachable) resolving 'linuxquestions.org/DS/IN': 2001:500:c::1#53
Mar 21 11:30:13 server-fedora named[15483]: error (network unreachable) resolving 'linuxquestions.org/DS/IN': 2001:500:48::1#53
Mar 21 11:30:13 server-fedora named[15483]: error (network unreachable) resolving 'linuxquestions.org/DS/IN': 2001:500:b::1#53

The number of errors like this are significantly high. In one day there are probably over 100. These are occuring while named is working and do not seem to cause named to stop. I found nothing in logs to indicate why named stops.

Are you using DNSSEC?

As best I can tell dnssec is not installed.

When I enter (as su -)
> dnssec-configure -s
I get command not found.

Upon further checking, I discovered that my named.conf file does enable dnssec. dnssec-validation is yes also.
bind-keys file and managed-keys-directory are also specified.

also, recursion is set to yes, if that matters.

Well the errors your posting have to do with dnssec. You might want to take the dnssec options out of named.conf and see if that resolves your issues. If it does and you want to use dnssec, then you can start AFTER you make sure bind is running correctly without it.

Thanks for the suggestions and info. I will try that and see how it does over a day or two.

HI,

unable to start named services for DNS
ERROR while starting services are.

umount:/var/named/chroot/var/named device is busy

I dont know how to kill that process.

could anybody tell me how to kill that process and i need to restart the named service.

Regards,
Rafiq.