Help Creating DHCP Server on Windows Server 2016

%3CLINGO-SUB%20id%3D%22lingo-sub-1546076%22%20slang%3D%22en-US%22%3EHelp%20Creating%20DHCP%20Server%20on%20Windows%20Server%202016%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1546076%22%20slang%3D%22en-US%22%3E%3CP%3EI%20need%20to%20configure%20a%20DHCP%20server%20to%20hand%20out%20IP%20addresses%20and%20DNS%20in%20a%20specific%20way%20see%20below%20how%20it%20should%20be%20handed%20out%3A%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3Edomain%20controller%3CBR%20%2F%3Eaddress%3A%20192.168.1.200%3CBR%20%2F%3Edefault%20gateway%3A%20192.168.1.254%3CBR%20%2F%3Esubnet%20mask%3A%20255.255.255.0%3CBR%20%2F%3EDNS%3A%20192.168.1.200%3CBR%20%2F%3EDNS%3A%20127.0.0.1%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3Eworkstation%201%3CBR%20%2F%3Eaddress%3A%20192.168.1.201%3CBR%20%2F%3Edefault%20gateway%3A%20192.168.1.254%3CBR%20%2F%3Esubnet%20mask%3A%20255.255.255.0%3CBR%20%2F%3EDNS%3A%20192.168.1.200%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3Eworkstation%202%3CBR%20%2F%3Eaddress%3A%20192.168.1.202%3CBR%20%2F%3Edefault%20gateway%3A%20192.168.1.254%3CBR%20%2F%3Esubnet%20mask%3A%20255.255.255.0%3CBR%20%2F%3EDNS%3A%20192.168.1.200%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThe%20Domain%20Controller%20is%20set%20up%20static%20on%20the%20network%20adapter%20and%20I%20would%20need%20the%20workstations%20to%20be%20assigned%20from%20the%20DHCP%20Server.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-1546076%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EActive%20Directory%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EManagement%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EWindows%20Server%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1546102%22%20slang%3D%22en-US%22%3ERe%3A%20Help%20Creating%20DHCP%20Server%20on%20Windows%20Server%202016%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1546102%22%20slang%3D%22en-US%22%3E%3CP%3EYou%20can%20follow%20along%20here%20to%20deploy%20a%20DHCP%20server.%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CA%20href%3D%22http%3A%2F%2Fwww.rebeladmin.com%2F2014%2F06%2Fstep-by-step-guide-to-install-dhcp-role-and-configure%2F%22%20target%3D%22_blank%22%20rel%3D%22noopener%20nofollow%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttp%3A%2F%2Fwww.rebeladmin.com%2F2014%2F06%2Fstep-by-step-guide-to-install-dhcp-role-and-configure%2F%3C%2FA%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3Ebut%20note%20if%20you%20already%20have%20a%20DHCP%20server%20(router)%20on%20the%20same%20network%20then%20there%20is%20a%20conflict%2C%20so%20I'd%20suggest%20if%20needed%20then%20put%20a%20personal%20NAT%20router%20in%20between%20windows%20domain%20and%20ISP%20equipment%20so%20you%20can%20have%20windows%20domain%20on%20its%20own%20network.%3C%2FP%3E%0A%3CP%3EThe%20other%20option%20may%20be%20to%20use%20the%20existing%20router%20to%20hand%20out%20the%20DC%20ip%20address%20(%3CSPAN%3E192.168.1.200)%20for%20DNS%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%3CSPAN%3E%26nbsp%3B%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E
Occasional Contributor

I need to configure a DHCP server to hand out IP addresses and DNS in a specific way see below how it should be handed out:

 

domain controller
address: 192.168.1.200
default gateway: 192.168.1.254
subnet mask: 255.255.255.0
DNS: 192.168.1.200
DNS: 127.0.0.1

 

workstation 1
address: 192.168.1.201
default gateway: 192.168.1.254
subnet mask: 255.255.255.0
DNS: 192.168.1.200

 

workstation 2
address: 192.168.1.202
default gateway: 192.168.1.254
subnet mask: 255.255.255.0
DNS: 192.168.1.200

 

The Domain Controller is set up static on the network adapter and I would need the workstations to be assigned from the DHCP Server.

1 Reply

You can follow along here to deploy a DHCP server. 

 

http://www.rebeladmin.com/2014/06/step-by-step-guide-to-install-dhcp-role-and-configure/

 

but note if you already have a DHCP server (router) on the same network then there is a conflict, so I'd suggest if needed then put a personal NAT router in between windows domain and ISP equipment so you can have windows domain on its own network.

The other option may be to use the existing router to hand out the DC ip address (192.168.1.200) for DNS