Best practice for defining static IP addresses?

Ryan McCain Ryan.McCain at dss.state.la.us
Wed Aug 6 14:23:38 UTC 2008


Todd,

Thanks for the info.  Do you have a link to your thread?  


>>> On Tue, Aug 5, 2008 at  4:02 PM, in message
<1D8C9A4471119A40BD574F9D8D464AE301B85A6C at XCH60YKF.rim.net>, "Todd Snyder"
<tsnyder at rim.com> wrote: 
> I thought this very same thing until a few months ago, and after bashing
> my head about for a while, I came here and was corrected.
> 
> Static assignments need to be outside any defined ranges.  This is
> different than Windows DHCP, which lets you 'reserve' an ip in the
> middle of range.
> 
> If you want to do the first option, you will have to define 2 ranges
> 
> range 10.119.14.1 10.119.14.99
> 
> and
> 
> range 10.119.14.101 10.199.14.179
> 
> Which isn't ideal.
> 
> Cheers,
> 
> Todd.
> 
> -----Original Message-----
> From: dhcp-users-bounce at isc.org [mailto:dhcp-users-bounce at isc.org] On
> Behalf Of Ryan McCain
> Sent: Tuesday, August 05, 2008 4:55 PM
> To: dhcp-users at isc.org
> Subject: Best practice for defining static IP addresses?
> 
> Lets assume this is my DHCP scope:
> 
> subnet 10.119.14.0 netmask 255.255.255.0 {
>   range 10.119.14.1 10.119.14.179 ;
>   option routers 10.119.14.254 ;
> 
> If I wanted to assign a static IP address, would I do?
> 
> host Black {
>   hardware ethernet 00:19:5B:EC:A7:11;
>   fixed-address 10.119.14.100;
> }
> 
> or
> 
> host Heart {
>   hardware ethernet 00:19:5B:EC:A7:12;
>   fixed-address 10.119.14.200;
> }
> 
> ..Notice that 'Black' is within the defined range while 'Heart' is not.
> 
> I've always assume I could assign a static IP within the defined range
> and the MAC address would act as a 'key' to prevent it from being handed
> out  (even though it's in a defined range).
> 
> Thanks for the clarification..
> 
> 
> 
> 
> 
> 
> 
> 
> ---------------------------------------------------------------------
> This transmission (including any attachments) may contain confidential 
> information, privileged material (including material protected by the 
> solicitor-client or other applicable privileges), or constitute non-public 
> information. Any use of this information by anyone other than the intended 
> recipient is prohibited. If you have received this transmission in error, 
> please immediately reply to the sender and delete this information from your 
> system. Use, dissemination, distribution, or reproduction of this 
> transmission by unintended recipients is not authorized and may be unlawful.



More information about the dhcp-users mailing list