How to synchronize dhcp statics / reservations between two domain controllers?

Hello all,

I have two windows 2003 server (both domain controllers, dhcp, and dns).  I know that it sychronizes and replicates dhcp by itself, but is there a way to auto-sync static IP addresses that you manually enter into the reservations so that both servers always have the same information?  For example, if I goto server1 and manually reserve an IP address, how do I make server2 also recieve that information without me having to do it?

Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Setting reservations only applies to that particular scope.

It's best practice to create separate scopes on each DHCP server, with different IP assignments, that way there isn't conflicts or bad information.

I'm actually unaware that DHCP servers in Windows sync their data between them...if so that's news to me.  I've always been under the impression that you created scopes on each server with different IP ranges simply because it doesn't replicate.

mainemontyAuthor Commented:
You are right Mr. Cleaner.  DHCP servers don't sync data, I misworded that and meant to say that wanted it to do so.  I am actually setting up 2 separate scopes on each DHCP server, but I'm just worried about all the static IPs that I reserve.  I need for a single exact copy of just the statics to exist between the 2 scopes.  I just wasn't sure if this was possible.  Basically if server1 (scope 0-100) goes down, I would still like for clientA (reserved IP of .50) to somehow maintain it's IP and connectivity, even though server2 has a scope of 101-200.  Maybe I'm just stretching, but just thought that I'd pose the question.


After 50% of the lease time has passed, the client will attempt to renew the lease with the original DHCP server that it obtained the lease from using a DHCPREQUEST message. Any time the client boots and the lease is 50% or more passed, the client will attempt to renew the lease. At 87.5% of the lease completion, the client will attempt to contact any DHCP server for a new lease. If the lease expires, the client will send a request as in the initial boot when the client had no IP address. If this fails, the client TCP/IP stack will cease functioning.

If you are really concerned about it, then you can create a separate scope on DHCP server #2 for the EXACT same scope and reservations as server #1 and leave it disabled/not started.

Then if server #1 does go down for some reason for any extended period of time, you just start the "reservations scope" on server #2.

Everyone else that was getting a normal DHCP lease on server1 will eventually end their lease and get a new IP from server #2 in the 101-200 range.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows Server 2003

From novice to tech pro — start learning today.