dhcpd.conf: three small nuisances

[Glenn Satchell]

>Date: Wed, 17 Jan 2007 09:16:19 -0500
>To: dhcp-users at isc.org
>Subject: Re: dhcpd.conf: three small nuisances
>Content-Disposition: inline
>From: rabbit at rabbit.us (Peter Rabbitson)
>
>On Thu, Jan 18, 2007 at 12:33:14AM +1100, Glenn Satchell wrote:
>> Don't convert to a string first - use the binary representation, eg:
>> 
>>     class "00:0a:e6:e9:91:72" {
>>         match if (substring (hardware, 1, 6)) = 0:0a:e6:e9:91:72;
>>     }
>> 
>
>Excellent. The answer is so obvious yet I didn't think of it.
> 
>> As for dns names. You can put entries in DNS and then refer to them by
>> name in dhcpd.conf, eg:
>> 
>> in DNS
>> 
>> foobar IN A 192.168.0.1
>> 
>> in dhcpd.conf
>> 
>> host foobar {
>>   hardware 00:0a:e6:e9:91:72;
>>   fixed-address foobar.example.com;
>> }
>> 
>
>Isn't this going to work only with host/fixed-address pairs? Besides

You still need to use dynamic dns updates for your pools and dynamic ranges.
 
>when adding a host I will still need to edit both the zone and the dhcpd 
>config. 

In the end I think it turns out to be much simpler than adding a *lot*
of complexity to dhcpd.conf. You have to use dynamic DNS for your name
server zones, so writing an add-host script that uses nsupdate becomes
relatively simple anyway. Just putting forward some ideas to consider...

regards,
-glenn