DHCP Bad address question

[david lazarus]

I am planning to implement 2 w2k3 DHCP servers for redundancy. I'd like to
have both servers setup with the same scope, exclusions etc as each other
and have only 1 of them authorised. The plan being that if the dhcp server
fails I can just authorise the 2nd server with the same scope and options.
(Before you mention it I know about split scopes). On both servers I plan on
setting the "conflict detection attempts" to 1.

If the server fails and I authorise the 2nd server. With DHCP conflict
detection enabled I expect that I will get BAD_ADDRESS entries in my DHCP
database, because addresses will exist on the network already.

My question is (based on the above senario), Does the DHCP server lease the
BAD_ADDRESS and after the lease period expires the entry is cleared and
becomes available again. OR are the BAD_ADDRESSES permanently kept on the
DHCP server and they need to deleted manually?

 

[Phillip Windell]

I am planning to implement 2 w2k3 DHCP servers for redundancy. I'd like to
have both servers setup with the same scope, exclusions etc as each other
and have only 1 of them authorised. The plan being that if the dhcp server

The best way is to have them identical as you say, *except* for the
Exclusions. Both would be fully operational and authorized. The Exclusions
would be arainged so that each server gives out half of the addresses (each
doing a different half of course). Of one goes down you simply delete the
exclusion on the remaining one so it can use all the addresses, when the
first is repaired, return the Exclusion to the way it was. At worse there
might be a very brief "hiccup" if a couple addresses are caught in the
transition, but that should be minor.

This is how I run ours here. I follow the same general principle here with
the DCs, DNS, WINS, and DHCP.

 

[david lazarus]

Thanks for your response Phil...Unfortunately it doesnt really answer my
question on whether the Bad_Address leases are permanent or leased for the
standard lease period