<div>
If all Domain Controllers are on different subnets, should not be an issue. But even if they are all on the same subnets, it really depends on how DHCP is configured on those Domain controllers. So without more details from you not sure how one defines &quot;Cause a conflict&quot;.
</div>


<div>
Multiple DHCP Servers on the same subnet are normally a bad idea, your clients will generate 4 times as much network traffic when searching for a DHCP Server to obtain an address, but as Etienne said, it depends on how DHCP is configured.<br />
<br />
DNS on 4 DC's won't cause any issues, only DHCP could provide a problem.
</div>


<div>
<blockquote>
Multiple DHCP Servers on the same subnet are normally a bad idea,
</blockquote>
<br />
depends on network topology<br />
we don't know how many clients there are<br />
should have at least 2 for redundancy<br />
4 dhcp servers might be overkill, but again don't know the network setup
</div>


<div>
Hi All<br />
<br />
I agree we've been having users with windows 7 pc issues whereby &nbsp;dns/dhcp are an issue.<br />
we been looging onto users machines &amp;&nbsp;running these commands &nbsp;ipconfig/flushdns plus ipconfig/release/renew in order for them to do any work.<br />
We do have a DC that has 2003 &amp;&nbsp;dhcp/dns are still enabled so the functional level isn't 2012
</div>


<div>
Functional level of AD is not relevant. It really would help to know how the DHCP is configured if you want help with this issue.
</div>


<div>
Hi Etienne,<br />
Yes id &nbsp;help please what would you like to know?<br />
Thank you
</div>


<div>
For each dhcp server, what are the dhcp scopes / pools / exclusion zones for each?<br />
<br />
Are all servers providing the correct DNS server and default gateway to the dhcp clients within the dhcp options?<br />
<br />
My initial thoughts are that two computers are being given the same ip address by different dhcp servers or possibly the dhcp options aren't configured correctly on one of the servers.
</div>


<div>
Hi Mdlinnett<br />
<br />
Please have a look at the SS provided I do agree with what your saying because we keep seeing on two different DC's the same IP/Computer name leased out at the same time &amp;&nbsp;we keep having to do a ipconfig/release &amp;&nbsp;ipconfig/dnsflush I order for the user to work on certain services<br />
<br />
Many thanks for your input<br />
<a href="https://filedb.experts-exchange.com/incoming/2016/08_w34/1111555/DHCP-Pool.docx" target="_blank" class="file-inline" title="DHCP-Pool.docx (85 KB)"><svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 512 512"><path d="M67.508 468.467c-58.005-58.013-58.016-151.92 0-209.943l225.011-225.04c44.643-44.645 117.279-44.645 161.92 0 44.743 44.749 44.753 117.186 0 161.944l-189.465 189.49c-31.41 31.413-82.518 31.412-113.926.001-31.479-31.482-31.49-82.453 0-113.944L311.51 110.491c4.687-4.687 12.286-4.687 16.972 0l16.967 16.971c4.685 4.686 4.685 12.283 0 16.969L184.983 304.917c-12.724 12.724-12.73 33.328 0 46.058 12.696 12.697 33.356 12.699 46.054-.001l189.465-189.489c25.987-25.989 25.994-68.06.001-94.056-25.931-25.934-68.119-25.932-94.049 0l-225.01 225.039c-39.249 39.252-39.258 102.795-.001 142.057 39.285 39.29 102.885 39.287 142.162-.028A739446.174 739446.174 0 0 1 439.497 238.49c4.686-4.687 12.282-4.684 16.969.004l16.967 16.971c4.685 4.686 4.689 12.279.004 16.965a755654.128 755654.128 0 0 0-195.881 195.996c-58.034 58.092-152.004 58.093-210.048.041z"/></svg>DHCP-Pool.docx</a>
</div>


DHCP-Pool.docx

<div>
Hi All<br />
can anyone help<br />
Thank you
</div>


<div>
Your screen shot only shows one of your DHCP server. But does not show the other DHCP server, given what you describe so far, you should &quot;disable&quot; one of the 2 DHCP servers......
</div>


<div>
Are all four of your DHCP servers configured as shown in the screenshot? Are the address ranges and exclusions identical on all of them? Also, I don't believe you've specifically said whether all four servers are on the same subnet.<br />
<br />
If all four servers are on the same subnet and have the same DHCP configuration, that's certainly redundancy, but it's not the good kind of redundancy. It can cause problems, as the first server to respond to a client request will be the one that assigns an address to that client. The servers don't share information with each other regarding the addresses they've assigned, so it is possible that the same address will be assigned to different clients by different servers. Conflict detection, if enabled, is supposed to minimize this, but it's better to configure the environment in such a way that it can't happen in the first place.<br />
<br />
If at least two of your DHCP servers are running Windows Server 2012 or 2012 R2, you may want to consider implementing <a href="https://technet.microsoft.com/en-us/library/dn338978(v=ws.11).aspx" rel="ugc">DHCP failover</a>. It provides redundancy for DHCP without the potential for conflict.<br />
<br />
If your DHCP servers are running older versions and you still want some form of redundancy, you should consider a <a href="https://technet.microsoft.com/en-us/library/ee405264%28v=ws.10%29.aspx" rel="ugc">split scope</a>, in which the address range is divided among two servers, and the second server is configured not to respond to requests right away. This effectively makes it a standby server that will only service clients if the primary server is unable to do so.
</div>


<div>
Your problem is in how DHCP operates. <br />
First it does a broadcast (address ff:ff:ff:ff:ff:ff, in a fabricated UDP packet destined for 255.255.255.255, source 0.0.0.0) on the network and it asks for the active DHCP (servers).<br />
Then ALL DHCP servers that receive such a packet will Respond that they are alive and capable to supply services. (if they are)....<br />
Then the client will choose one server (Mostly the one that responds first to the query). and continue talking to it.<br />
All this conversation is still Ethernet level, with faked IP info, not having a valid IP address yet...<br />
<br />
So there is DEFINITELY no knowledge on the DHCP client about windows networks, routing topology etc. (until the DHCP sequence is completed).<br />
With multiple DHCP servers on a single broadcast domain (ie. an ethernet (V)LAN) &nbsp;there should be none that supplies addresses from a range, all should only handout reservations.<br />
(As that will prevent them from responding to others). But that almost defeats the purpose of DHCP.<br />
<br />
After IP is up (DHCP is completed) the kerberos &amp;&nbsp;LDAP queries can be started.
</div>


<div>
Hi <br />
<br />
Thank you all!. Can I now ask how I would beginning to start phasing at least two of the current DHCP servers?<br />
<br />
Thank you
</div>


<div>
Hi Mark,<br />
<br />
It depends on the answers to the questions asked of you since you posted the screenshot of one of your DHCP Servers.<br />
<br />
Is your DHCP Pool the same on each of your 4 DHCP Servers?<br />
<br />
If so, deactivate the DHCP Servers you don't want to use and, if necessary, remove the DHCP role.<br />
<br />
If 2 of your Servers are running Server 2012 or 2012 R2 then true DHCP failover can be configured. &nbsp;See the following Microsoft Article, specifically the section on 'Configure a Failover Configuration' &gt;&nbsp;<a href="https://technet.microsoft.com/en-us/library/hh831385(v=ws.11).aspx" rel="ugc">https://technet.microsoft.com/en-us/library/hh831385(v=ws.11).aspx</a><br />
<br />
If not 2012, the same article discusses split scope DHCP which I believe is what you would need to use if you intend on keeping 2 DHCP Servers on the same subnet.
</div>


<div>
Hi <br />
When phasing out one dchp server is it worth putting a 0 on the lease time duration &amp;&nbsp;then disabling one then the other?<br />
thank you for you're help
</div>


<div>
id like to give all points to all contributors because all were completely helpful &amp;&nbsp;made me understand dhcp so much better thank you
</div>


<div>
<div class="content wysiwyg-content">
Hi All We have one PDC &amp;&nbsp;three other associated with it we have dchp enabled on all Domain Controller can this cause a conflict<br />
thank you all for your support
</div>
</div>


Hi All We have one PDC & three other associated with it we have dchp enabled on all Domain Controller can this cause a conflict
thank you all for your support

Four DHCP servers &amp; Four DNS Sever on Four Different Domain Controllers

The Dynamic Host Configuration Protocol (DHCP) is an auto configuration protocol used on IP networks and an extension of the Bootstrap Protocol. DHCP allows for computers to be configured automatically to communicate with each other over an IP network without the need for manual setup by a network administrator. The implementation of DHCP relies on a DHCP server to hand out network configuration information to DHCP-capable clients that request an IP address (and other information required or useful in communicating with other devices on an IP network). In addition to an IP address, common configuration information served over DHCP includes a default gateway, subnet mask and DNS sever(s).

DHCP

The Domain Name System (DNS) is a hierarchical, globally distributed system responsible for associating the name of a computer, service or other resource into an IP address for connecting to the Internet or a private network. Most prominently, it translates domain names to the numerical IP addresses needed for the purpose of computer services and devices worldwide.

The Windows operating systems have distinct methodologies for designing and implementing networks, and have specific systems to accomplish various networking processes, such as Exchange for email, Sharepoint for shared files and programs, and IIS for delivery of web pages. Microsoft also produces server technologies for networked database use, security and virtualization.

Windows Networking

Active Directory (AD) is a Microsoft brand for identity-related capabilities. In the on-premises world, Windows Server AD provides a set of identity capabilities and services, and is hugely popular (88% of Fortune 1000 and 95% of enterprises use AD). This topic includes all things Active Directory including DNS, Group Policy, DFS, troubleshooting, ADFS, and all other topics under the Microsoft AD and identity umbrella.

Four DHCP servers &amp; Four DNS Sever on Four Different Domain Controllers

Four DHCP servers & Four DNS Sever on Four Different Domain Controllers