This is a discussion on RE: Chrooting Bind 9 issue within the Bind Users forums, part of the DNS and Related Forums category; The problem is that the -c option which lists the path to the config file should be relative your chroot ...
|
|||||||
| FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
|
|||
|
The problem is that the -c option which lists the path to the config file
should be relative your chroot directory. Get rid of /var/chroot and make it -c /etc/named.conf and that should address the problem. Also make sure the directory option in named.conf is only listed as /etc as well. - Bill -----Original Message----- From: M Alan C [mailto:my00sc00by@yahoo.com] Sent: Thursday, May 27, 2004 8:25 AM To: bind-users@isc.org Subject: Chrooting Bind 9 issue I am running this: /var/chroot/sbin/named -u resolver -t /var/chroot -c /var/chroot/etc/named.conf and I am still getting this: May 27 12:21:50 nameserver named[414]: [ID 873579 daemon.error] none:0: open: /var/chroot/etc/named.conf: file not found May 27 12:21:50 nameserver named[414]: [ID 873579 daemon.crit] loading configuration: file not found May 27 12:21:50 nameserver named[414]: [ID 873579 daemon.crit] exiting (due to fatal error) my permissions are set to this: -rwxr-xr-- 1 resolver named 3277 May 25 06:09 named.conf -rwxr-xr-- 1 resolver named 247 May 24 12:35 rndc.conf why is this not working? how can I fix this? Mark "Hamzter" C kd5zmg --------------------------------- Do you Yahoo!? Friends. Fun. Try the all-new Yahoo! Messenger |
![]() |
| Thread Tools | |
| Display Modes | |
|
|