I am failing to get Named started. I copied my named.custom and zone files to a diskette from my 3.3 build. I installed 4.0 from scratch and did the updates. I edited /etc/named.conf (which I realize is a link) to include named.custom I cp named.custom into /etc (all of this was done while logged in as root) When I try to start named from the services GUI (using GNOME) and I get this error: named failed. The error was: Starting named: /etc/named.conf:67: open /etc/named.custom: file nto found /etc/init.d/named: line 56: [: too many arguements [FAILED] So what is wrong. /etc/named.custom is there. permissions look right. All done as root. Am I suppose to put named.custom in the croot area along with named.conf and set up a symbolic link (which I have forgotten how to do, as I haven't done it since '93)?
* Robert Moskowitz <rgm at htt-consult.com> [2005-03-30 15:55:16]:> > Am I suppose to put named.custom in the croot area along with > named.conf and set up a symbolic link (which I have forgotten how to > do, as I haven't done it since '93)?If you are running a chroot, then yes, you will need to have that file in the chroot environment as well otherwise named won't be able to read it. Matt -- "If there are no spots on a sugar cube then I've just put a dice in my tea." -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 186 bytes Desc: not available URL: <http://lists.centos.org/pipermail/centos/attachments/20050330/32429fa4/attachment-0005.sig>
Robert Moskowitz wrote:> I am failing to get Named started. > > I copied my named.custom and zone files to a diskette from my 3.3 build. > > I installed 4.0 from scratch and did the updates. > > I edited /etc/named.conf (which I realize is a link) to include > named.custom > > I cp named.custom into /etc (all of this was done while logged in as root) > > When I try to start named from the services GUI (using GNOME) and I get > this error: > > named failed. The error was: Starting named: /etc/named.conf:67: open > /etc/named.custom: file nto found > /etc/init.d/named: line 56: [: too many arguements [FAILED]My guess is you have bind-chroot installed (good thing). If so, named is running in chroot jail, and can't access real /etc directory. What named will see as /etc is what you see as /var/named/chroot/etc. So you need to place your *real* named.custom file inthere. For convinience you may (if you want) create symbolic link to it from /etc. Note that creating symbolic link from /var/named/chroot/etc to files in /etc will not work. Named will see link pointing to /etc/named.custom. Since it is running in chrooted jail, it will try to access what it sees as /etc/named.custom (which really is /var/named/chroot/etc/named.custom). So basically, it will see symbolic link pointing to itself. -- Aleksandar Milivojevic <amilivojevic at pbl.ca> Pollard Banknote Limited Systems Administrator 1499 Buffalo Place Tel: (204) 474-2323 ext 276 Winnipeg, MB R3T 1L7