Network Cloud family blueprint deployments involves a number of different DHCP servers.

During deployment

The RC makes a DHCP Request which must be Responded to by the Build Server via the 'host' network L2 domain.
Rover servers and Unicycle genesis nodes make DHCP Requests over the WAN spanning between the edge site and the RC's more centralized location which must be Responded to by the RC via the 'host' L2 domain. In the R1 release the 'host' network is a single L2 broadcast domain. It is possible to split the WAN host network into multiple routed L2 domains using functionality such as DHCP helper/relay but this is unverified in R1.
Unicycle masters and workers (all unicycle nodes other than genesis), make DHCP Requests via the edge site's local 'pxe' network's L2 broadcast domain which must be Responded to by the genesis node's MaaS DHCP server .

HTTP PXE / PXE Booting

...

During deployment
The RC are configured by the Redfish API calls issued by the Build Server to HTTP PXE boot from the Build Server over the 'host' network.
Rover servers and Unicycle genesis nodes are configured by the Redfish API calls issued by the RC to HTTP PXE boot from the RC over the 'host' network.
Unicycle masters and workers (all unicycle nodes other than genesis), are configured by the MaaS server running on the genesis node to PXE boot over the remote sites 'pxe' network.<DHCP FLOWS FOR RC → BUILD SERVER; ROVER/GENESIS →RC; UNICYCLE MASTER2/3 →GENESIS(MAAS)>