D
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?
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?