On 09/14 01:02 , Jim Summers wrote: > Ideas / Suggestions? If at all possible, use static DHCP assignments. this will make your life as a sysadmin much easier, since you'll be able to know what user has which machine. (you can set up DNS to associate bill.int.yourcompany.com with Bill's computer, etc).
It's not much work to set up static DHCP assignments. Just get the MAC of the machine in question (and you can get it from your DHCP logs). If you're really adventurous, you can use Dynamic DNS to accomplish much the same thing, but IMHE it's a bit fragile, and if you own the network and all the computers on it, static DHCP and DNS is much more robust. As an unrelated 'good practices' suggestion, if you're not familiar with it already, put your privately-addressed hosts on a separate subdomain from your public hosts. So your hosts with public addresses are host.yourcompany.com, whereas the hosts behind your firewall should be host.int.yourcompany.com. This avoids the ugliness, fragility, and information leaks of split-horizon DNS. -- Carl Soderstrom Systems Administrator Real-Time Enterprises www.real-time.com ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ BackupPC-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/backuppc-users http://backuppc.sourceforge.net/
