Darren J Moffat writes: > James Carlson wrote: > > David Lloyd writes: > >> My issue isn't with the DHCP server. In fact, if I get my setup from the > >> DHCP server, DNS works. It's just that the DNS it gives me is really bad > >> [1]. > > > > That's a solvable problem. I have something like this in my > > /etc/dhcp/eventhook script (owner root, mode 755) because I run a > > local caching named, and I want to make sure that it's used: > > I curious why you do this when we have nscd, care to share ?
Though I also leave nscd running, (A) I don't like nscd, not one bit, (2) I also have my own domain and do zone transfers to secondaries, (III) nscd doesn't know beans about MX records, and (four) nscd can't answer queries from other local systems. Nscd is a fair answer if the problem you're trying to solve is the overhead of going out to your local NIS server on every single getpwuid() call -- it makes sense on the SWAN. It's a feeble answer if you have unreliable external name servers, or you care about the DNS TTL, or you want to have one machine behave as a local cache for other systems. Running your own caching in.named is simple and highly effective. I'd be surprised to find other Internet-connected systems (such as the one where I run that eventhook script) that rely on _just_ nscd. I suppose it's possibly tolerable if your ISP is really, really good, but I doubt it. -- James Carlson, KISS Network <[EMAIL PROTECTED]> Sun Microsystems / 1 Network Drive 71.232W Vox +1 781 442 2084 MS UBUR02-212 / Burlington MA 01803-2757 42.496N Fax +1 781 442 1677 _______________________________________________ opensolaris-discuss mailing list [email protected]
