Greetings,
DHCP is one of the simplest tools to use, but equally once one steps outside of the 'typical' or 'default' settings, it can be cumbersome. I have had some pain in this area, so i went out and dug as deep as possible.
Here are a couple of things of importance:
1. DHCP is based on bootp.
2. The machine, once it receives an IP, doesn't wait until the end of the lease to get a new one. the machine will contact the server multiple times as the lease expires - you can get a better explanation on a wiki elsewhere, but understand it does do so.
3. DHCP, unless the machine is on the same subnet, is typically proxied by the router.
the process . . .
A machine yells "I need an address."
The router hears it, picks it up, forwards it to the proper server, waits for the address and delivers it back to the machine.
~And it happens quickly~
First, i would check the scope.
It appears that you have reserved addresses that are covered in a static form, but also available to machines needing an address.
Remove all of the static IPs by creating a subnet template that excludes a certain amount of addresses.
This will be company-specific as well as subnet-specific.
Since we will be making the template, lets jump ahead and assume that we want 2 scopes for the subnet.
You wil need to turn on DHCP on a second server in the network - preferably on a different subnet than the first, as this will help redundancy and as an alert mechanism.
To do this, we will need the network team to add the second DHCP server to the interface.
They should know how to do this.
anyway, so here is our template.
An example:
Scope #1 on DHCP server #1
172.16.23.x /24
.1 - .5 - router/switch static (exclude from scope)
.6 - .10 reserved (exclude from scope)
.11 - .20 printers (exclude from scope)
.21- .121 lease addresses
.122 - .254 reserved (exclude from scope)
Scope #2 on DHCP Server #2
172.16.23.x /24
.1 - .5 - router/switch static (exclude from scope)
.6 - .10 reserved (exclude from scope)
.11 - .20 printers (exclude from scope)
.21- .121 reserved (exclude from scope)
.122 - .254 lease addresses
when machines yelp for an address, typically the router sends to the DHCP servers and the server to respond first, gets the address.
placing the second scope in a remote data center for redundancy, almost ensures that the nearer server replies quickly.
after .21 through .121 in the example are provided addresses, .122 will be served from the second server.
this will occur until it hits .254
This will help in two ways.
1. DR - if the first DHCP ever tanks, a second server can jump right in.
2. Troubleshooting - if you see devices with IP addresses above .121 even though the first server has addresses available, something is interfering, slowing down, etc.
Another Tip - it is possible to deliver so much more than the simple IP address, gateway and DNS.
Check out all of the different options and you may find something of value you may have needed for a while.
Drop a note or find me on linked in if i can help some more.