Accidentally restarted named (version 9.2.4-2 ) trowed an error

scenario

restarted named (version 9.2.4-2 ) trowed an error

"Error in named configuration:
none:0: open: /etc/named.conf: file not found"

tail -f /var/log/messages shows
kernel: 0: @f66e7200 length 8000059a status 0c01059a
kernel: 2: @f66e7340 length 80000036 status 00010036
kernel: eth0: Transmit error, Tx status register 82.
kernel: Probably a duplex mismatch. See Documentation/networking/vortex.txt
kernel: Flags; bus-master 1, dirty 1997587141(5) current 1997587141(5)

But the named .conf exists ... checked the permission that is also ok !

tried using yum installing bind
Downloading Packages:
(1/1): bind-devel-9.2.4-2 100% |=========================| 2.2 MB 00:18
Running Transaction Test
Finished Transaction Test
Transaction Test Succeeded
Running Transaction
Installing: bind-devel ##########
[root@cobalt171 etc]# service named start
Starting named:
Error in named configuration:
none:0: open: /etc/named.conf: file not found
[FAILED]
..still no luck .

ANSWER

I found that the server is been updates to chroot environment that is not default in EL4
So the mess is chroot .
Did the following steps
rpm -e bind-chroot
ln -sf /var/named/run-root/etc/named.conf /etc/named.conf ( making the link for named.conf)
/etc/init.d/named restart
Stopping named: [FAILED]
Starting named: [ok]
Issue fixed