DHCP and Dynamic DNS for SSL machines

New SSL lab machines should all be behind Apu, which acts as DHCP, DNS, and NFS server for SSL lab machines. To add a machine to the lab, after installing the hardware according to lab Installation Policies, all you need to do is have an entry for the machine added to /etc/dhcp3/dhcpd.conf on Apu. This machine should contain the hardware address for the machine (so “dhcpd” knows which entry to give you information about), the IP address for the machine (give it a 10.0.X.X address appropriate to the rack in which it lives, please), the hostname for the machine (an option host-name entry), and the DDNS hostname for the machine (a ddns-hostname entry) so that dhcpd can add your machine to the DNS server when it comes up.

Here's an example entry, in this case for wendell, a machine in the Kwik-E mart rack (all machines in Kwik-E Mart have 10.0.1.X addresses):

host wendell {
        hardware ethernet 00:14:4F:02:59:AE;
        fixed-address 10.0.1.101;
        option host-name "wendell";
        ddns-hostname "wendell";
}

On Apu itself to serve this information, the setup is somewhat more complicated. There's a good bit of information on the web, but here are a few gotchas:

1. You need to include the update-static-addresses in ”/etc/dhcp3/dhcpd.conf” to make Dynamic DNS (ddns) work for preassigned IP addresses as well
2. Each machine needs to either have a ddns-hostname entry in the DHCP file so that “dhcpd” knows that you want it to go into DNS (recommended) or needs to tell dhcpd it's hostname when it asks for a lease