On Sun, 2011-07-31 at 22:03 -0500, Robert Nesius wrote: > On Sat, Jul 30, 2011 at 6:19 PM, Tony Yarusso <tonyyarusso at gmail.com> wrote: > > > DNS does not assign addresses - DHCP does. > > > He can assign the address in DNS as long as he sets the ip address > statically on the client. > > Perhaps I'm just being pedantic. :) I tend to prefer DHCP reservations > myself. > > -Rob > > > > You need to add two things > > to your dhcpd.conf. First, tell it that 164 is an exception to the > > pool range (so it doesn't try to hand that out to any other machines). > > Then, tell it to always give 164 to the machine with a MAC address > > matching that of the client in question (a "static lease"). > > > > - Tony Yarusso > > _______________________________________________ > > TCLUG Mailing List - Minneapolis/St. Paul, Minnesota > > tclug-list at mn-linux.org > > http://mailman.mn-linux.org/mailman/listinfo/tclug-list > > > _______________________________________________ > TCLUG Mailing List - Minneapolis/St. Paul, Minnesota > tclug-list at mn-linux.org > http://mailman.mn-linux.org/mailman/listinfo/tclug-list Tony is right, I needed DHCP to set the addresses on the clients. What I am trying to do is to let the computers here to get their addresses via an automated process. The static addresses are needed to let nfs securely attach. I still need to set the DNS server addresses manually at each client - that is the next nut to crack. I got DHCP to do that (verifying each machine by it's mac). Now I would like (need) to get the caching DNS working. That may speed up connecting to the internet sites that I am interested in. Well, a deep breath here and back into the fray. tayl Neal