Originally posted by deanrantala
do I enter my external ethernet IP? Or do I use the internal (LAN) IP here?
Your internal (LAN) IP. It has to be an IP address that the clients can find via ARP -- in other words, an address on the local LAN -- because they don't know of a router address to use to get to it.

I got that part right didn't I ?
Yep.

Now for this, I assume I need to enter "tampabay.rr.com"?
Yes.

Is this actually needed?
I'm actually not sure. I have it in there, just to make sure that my DHCP clients can ping by hostname rather than IP address (my internal DNS server won't resolve just "alpha", for example, but it will resolve "alpha.mydomain").

And am I even using the right domain name? are there rules for picking a domain name?
As long as nobody outside your network can talk to your DNS server, then no, there aren't any rules. But if there's even a slight chance that they can, then there are rules for choosing a domain name. Basically, you have to pay a registrar for it. But it sounds like you already did, so that ought to be all right.

this is pretty self-explainatory - right? Just plug in my DNS server list?
Yep. Well -- your DNS server. I'm not sure if it can take a list or not (maybe that's been fixed in later dhcpd releases though).

As for putting it in the subnet section vs. not, I'm not positive on that either. I have it in my subnet section, and it works. But I'd expect that as long as you'll only ever serve one subnet for DHCP (and duh, it makes sense that that'd be the case), then it won't metter.