DHCP Best Practice in Virtual Setup

What is the best way to handle DHCP on my network. I have two physical domain controllers. I also have two Hyper V servers that run my virtual servers. Currently my router is temporarily handling DHCP.

The domain controllers are a primary and backup with DNS. If i install DHCP on one of those servers I can only do it on one.  I don't think DHCP replicates to the other dmc.

Or could I create a cluster and have DHCP failover some how if one goes down? I never heard of anyone clustering domain controllers because they automatically replicate.

Or would it be better to create a third domain controller that was virtual machine? What is the best way to do this. I also want to add NTP time adjustment for network. I figured where ever i put the DHCP I would put NTP.
MEATBALLHEROAsked:
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.

Joseph DalyCommented:
You could take a look at using a split scope between the two dhcp servers.

http://blog.thesysadmins.co.uk/configuring-dhcp-split-scope-in-server-2008-r2.html
0

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
Seth SimmonsSr. Systems AdministratorCommented:
you didn't specify what version of windows you have
if 2012, you can do dhcp in failover cluster if you meet the system requirements for your servers

Step-by-Step: Configure DHCP for Failover
http://technet.microsoft.com/en-us/library/hh831385.aspx

in previous versions this was not possible; and you are correct, dhcp doesn't replicate since it's not AD integrated like DNS.  if you have earlier than 2012, then split scope as mentioned above is a good solution

as far as your time server goes, configure it on the domain controller that has the PDC emulator role

How to configure an authoritative time server in Windows Server
http://support.microsoft.com/kb/816042
0
bbaoIT ConsultantCommented:
> If i install DHCP on one of those servers I can only do it on one.  I don't think DHCP replicates to the other dmc.

DHCP does not work in the same way as DC. it does not replicate its scope to other DHCP servers.

> Or could I create a cluster and have DHCP failover some how if one goes down?

yes, you can. as a critical network services for LAN, DHCP failover should be considered. a DHCP cluster is an option, an easier way to do that is to use the 80/20 design rule for balancing scope distribution of addresses. see below the details.

DHCP Best Practices
http://technet.microsoft.com/en-us/library/cc780311%28v=ws.10%29.aspx

> I never heard of anyone clustering domain controllers because they automatically replicate.

DC can be clustered too. the clustered two nodes (or more) do not replicate AD info to each other as they are acting like a single computer. from the point of view of other client computers, they are a single server sharing the same IP address and server name.

a physical cluster is just a locally single computer.

> Or would it be better to create a third domain controller that was virtual machine?

DHCP services have no problem to be virtualised.

> What is the best way to do this.

Read the above official best practice.

> I also want to add NTP time adjustment for network. I figured where ever i put the DHCP I would put NTP.

NTP server can be assigned to the client computers by adding its DHCP options. see below DHCP Option 42 for details.

DHCP Tools and Options
http://technet.microsoft.com/en-us/library/dd145324%28v=ws.10%29.aspx
0
Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

KwoofCommented:
This is only available in Server 2008 R2 and Server 2012.  If you have older servers then you can accomplish in a similar fashion by putting having each server handle enough address for the whole network that are on the same subnet such as 10.0.1.1-250 on one server and 10.0.2.1-250 on the other, but with the same 255.0.0.0 subnet.
0
MEATBALLHEROAuthor Commented:
I have 2008 Server R2 with SVC pack 1 and all updates
0
Seth SimmonsSr. Systems AdministratorCommented:
in that case splitting your scope is your best way to go for redundancy
0
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
Active Directory

From novice to tech pro — start learning today.