View Full Version : Bind not working
radioguy
15th August 2005, 18:34
I noticed my Bind-server is off line. I just noticed it, so I'm not sure how it was broke or if it is. When I restart named, I get this message.
Aug 15 08:29:19 server named: /etc/named.conf:5: change directory to '/var/named/chroot/var/named' failed: file not found
Aug 15 08:29:19 server named:
Aug 15 08:29:19 server named: /etc/named.conf:5: parsing failed
Thanks for your help.
till
15th August 2005, 19:17
I noticed my Bind-server is off line. I just noticed it, so I'm not sure how it was broke or if it is. When I restart named, I get this message.
Aug 15 08:29:19 server named: /etc/named.conf:5: change directory to '/var/named/chroot/var/named' failed: file not found
Aug 15 08:29:19 server named:
Aug 15 08:29:19 server named: /etc/named.conf:5: parsing failed
Thanks for your help.
Is the file /etc/named.conf there?
radioguy
15th August 2005, 20:22
Yes its there here are the contents:
options {
pid-file "/var/named/chroot/var/run/named/named.pid";
directory "/var/named/chroot/var/named";
auth-nxdomain no;
/*
* If there is a firewall between you and nameservers you want
* to talk to, you might need to uncomment the query-source
* directive below. Previous versions of BIND always asked
* questions using port 53, but BIND 8.1 uses an unprivileged
* port by default.
*/
// query-source address * port 53;
};
//
// a caching only nameserver config
//
zone "." {
type hint;
file "named.ca";
};
zone "0.0.127.in-addr.arpa" {
type master;
file "named.local";
};
zone "111.168.192.in-addr.arpa" {
type master;
file "pri.111.168.192.in-addr.arpa";
};
zone "cumuluseugene.com" {
type master;
file "pri.cumuluseugene.com";
};
//// MAKE MANUAL ENTRIES BELOW THIS LINE! ////
falko
15th August 2005, 21:12
I guess the directory /var/named/chroot/var/named is missing?
radioguy
15th August 2005, 21:19
Actually, it is there. Here are the contents:
chroot localdomain.zone named.broadcast named.ip6.local named.zero pri.cumuluseugene.com slaves
data localhost.zone named.ca named.local pri.111.168.192.in-addr.arpa pri.https:
falko
15th August 2005, 21:22
I think this has to do with the fact that your Bind is running chrooted. Maybe some symlink that's missing... :confused:
radioguy
17th August 2005, 03:23
I had a file permission problem. All is good now.
silviuchingaru
6th October 2005, 16:41
How did u solved? because I'm haveing the same problem...
Simulacra
3rd November 2005, 02:45
I have run into the same issue. It does seem to be a permissions issue with the chroot jail. No response from the poster, so if anyone has any information I would greatly appreciate your help.
Thanks
Simulacra
7th November 2005, 03:46
I ventured back to the manual. Although everything was done properly during the installation, for some reason the permissions set for Named did not stay. I simply chmod'd the directories as the guide instructed and Bind was working again.
Brian
fobicodam
24th April 2006, 02:42
i tried that and still getting the cant find file error... i knew linux was unestable but not that much !!!! how can i fix it ?!??! please !!!! 5 minutes testing it and it just fall with no reason !!!! :mad:
falko
24th April 2006, 10:54
Do you have any errors in your log files or when you restart BIND?
22hosting
24th April 2006, 17:53
If you are working in a CHROOT'd environment you need to make sure that it has access to certain files outside that directory. At a guess I would say you need to make this directory available : /var/named/chroot/var/named
vBulletin® v3.7.4, Copyright ©2000-2009, Jelsoft Enterprises Ltd.