Good point. I keep thinking about installing a caching DNS server, then promptly forget about it. This would only handle half my situation though.
As Curtis mentioned, I should probably dig into Kerebos as well, though I think it's a bit much right now. I want to be secure though, so I'll at least investigate it. This isn't a critical thing at this time, it's more for my own convenience, so I do have time to investigate/research/hack together a solution. Curtis, wrt LDAP, you're right, I only need a couple of accounts set up for single login. BUT, I can see real potential in using LDAP for other things as well. Maybe store my contacts there, and/or some other such data, then export it to a "public" LDAP directory for use in web pages. Also, by taking this step, I can forsee at least one custom application I use that can integrate with Active Directory (which is just the MS version of LDAP, more or less) to simply use the Windows authentication information for the current user. But, LDAP only handles the authentication end of things. I still need to handle file access, so I'll be digging into NFS as well. Shawn On Tuesday 12 October 2004 21:54, Aaron Seigo wrote: > > for that i usually just set up a local DNS server and set it as the DNS for > the local network. you get nice, local DNS caching for free that way too =) > > you can put known hosts in LDAP but i find DNS to be faster _______________________________________________ clug-talk mailing list [EMAIL PROTECTED] http://clug.ca/mailman/listinfo/clug-talk_clug.ca Mailing List Guidelines (http://clug.ca/ml_guidelines.php) **Please remove these lines when replying
