IPv4 private address assignment

Posted by helloworld922 on Server Fault See other posts from Server Fault or by helloworld922
Published on 2012-11-02T09:37:15Z Indexed on 2012/11/02 11:03 UTC
Read the original article Hit count: 272

Filed under:
|
|

I'm working on a private network which uses static IPv4 addresses as well as DHCP addressing for the physical LAN network.

At a previous company I worked at they would assign static addresses in the 10.*.*.* space and all DHCP/LAN addresses were assigned in the 192.168.*.* space. Both of these address spaces are defined in the IPv4 private address space and there were never any internal conflicts.

From personal experience at home, school, at work, and pretty much any other machine I've dealt with extensively (Windows and a few Linux distros), the DHCP server would always by default choose an address from the 192.168.*.* address space.

Now my question is can I rely on this behavior? Do DHCP servers always by default assign from the 192.168.*.* pool (or any pool other than the 10.*.*.* pool), leaving the 10.*.*.* pool free for private static addressing? If not, under what conditions might a DHCP server choose an address in the 10.*.*.* address space?

© Server Fault or respective owner

Related posts about dhcp

Related posts about static-ip