- Dynamic DNS
- Of Masters and Slaves
- Accepting and Doing Updates
- TSIG
- The Dynamic Zone
- The Client
- Update Prerequisites
- Update Actions
- Using nsupdate
- Slave Server Issues
- Reverse Zones
- A One Host Zone
- DHCP
- Mixing DNS and DHCP Implementations
- DHCP and Static DNS Entries
- DHCP and Dynamic DNS Entries
- Dynamic Updates by the Client
DHCP and Dynamic DNS Entries
As I mentioned earlier, version 3 of the ISC DHCP distribution can do dynamic updates of DNS based on the hostname the client wants. However, the how of this integration has not been entirely worked out at this time so I'll refrain from teasing you with what you can't do. The DHCP Handbook has more information about how it is supposed to work.
The DNS update conditionals allow the DHCP server to specify update conditions to the DNS server such as "if the name already is in use" to forbid users from using new names or "if the name is not present" to forbid users from using names already in use. Whichever way you want it is a pure administrative decision and what you can allow depends on how much you trust your users. If you don't trust your users, I recommend that you give them static names.