Differences

This shows you the differences between two versions of the page.

--- networking:dhcp [2021/06/14 11:45] – bstafford
+++ networking:dhcp [2025/09/19 20:35] (current) – bstafford
@@ Line 2: / Line 2: @@
 Also, remember the port flow:
   * client to relay source udp-68 to udp-67
-  * relay to server udp-67 to udp-67
+  * relay to server udp-67 to udp-67 (initial request and T2 request)
   * server to relay udp-67 to udp-67
   * relay to client udp-67 to udp-68
+  * client direct to server udp-68 to udp-67 (T1 request. Blocked by Azure)
+=====DHCP Relay =====
+[[https://www.netmanias.com/en/post/techdocs/6000/dhcp-network-protocol/understanding-dhcp-relay-agents|Guide]]
+[[https://techcommunity.microsoft.com/blog/azurenetworkingblog/custom-dhcp-support-in-azure/4089674|Microsoft Guide]]
 =====DHCP Option Codes=====
@@ Line 40: / Line 45: @@
 Simply setup your scope options for your new Windows Server 2012 DHCP server and then Authorize it within your domain and the  migration is complete. (The GUI should give you a prompt on what to do)
+===== DHCP HA =====
+Split scope (in IPv4) is not efficient. When one server is down, capacity is reduced by half and clients cannot renew with the remaining server. It forces clients using the failed server to go to DHCPDISCOVER and that may cause disruption to the clients as they will change IP address.
+In IPv6, split scope works well because you have such huge IP address scopes.