Re: DNS mods?

["Aaron D. Turner" <aturner@best.com>]

-----BEGIN PGP SIGNED MESSAGE-----


Don't worry about... I figured it out.  There was some missing
directores/symlinks for the chroot environment to work properly.  It
needed a recursive link to /home/named.  

I see one problem with the symlink idea- RCS.  When you check out a file
in RCS it deletes the existing file and then creates a new one.  Hence any
symlinks you have get deleted and the changes you make are to a file that
doesn't get read by named.  Merging the changes back in seems like more
work than it's worth.

Let me explain:

ln -s /home/named/var/named/named.conf /etc/named.conf
ln -s /home/named/var/named/RCS/named.conf,v /etc/RCS/named.conf,v
cd /etc
co named.conf
ls -alF named.conf
- -r--r--r--   1 root     root         2475 Jan 16 13:50 named.conf  

Oops.  I bet when you check the file back in, it deletes the symlink in
RCS too.

Doing a symlink for named.pid is alright, but the init.d/named script
doesn't look there.

 On Sat, 16 Jan 1999, Jason Pincin wrote:

> > Uh, someone been playing with named??  It doesn't start anymore...
> > Complains about a missing directory that actually does exist.
> > Curious minds wanna know and all that.
> 
> No.  I emailed you about the dirs but did nothing with it.  The only
> modifications I made were to named.conf (placed another secondary in
> there) and to the linuxkb.org zone file.  You can check out my changes in
> both files.  Let me know if you find something as I'm about to submit
> changes to the Internic.  I added the DNS hosts to Internic already.
> 
> Jason
> 
> 


-----BEGIN PGP SIGNATURE-----
Version: 2.6.2

iQCVAwUBNqEKQzM3jpXy1kJtAQFoJAQAoKwCvEzCFT1VgEPBHgFRN+4eEojdIFry
Miv5zFib2uI3E2SV+bqdy78Kef04PpsMr1dFeNky5922fcJfWbr3DLhZJgcUagWS
t//4Ije3JCyWiwN/TCXTXePBaw5zov7rxS7O8apSI0yC518SZhULQQAdTWHXZEdR
IGZUV99hW+4=
=KMMU
-----END PGP SIGNATURE-----