Plan to create an Organizational Unit (OU), Country (C), or Locality (L) container object near the top of your eDirectory tree. Plan to locate the DNS/DHCP Group and Locator objects under the container object.
The DNS/DHCP Locator object must be easily accessible to all DHCP servers on the network. Plan to have multiple routes for DHCP servers to access the DNS/DHCP Group object.
Create Subnet objects to represent each LAN segment. Then create one or more Subnet Address Range objects to represent all your contiguous strings of IP addresses.
Place the NetWare Core ProtocolTM (NCPTM) servers that will provide DCHP service near the data to be updated and close to a writable partition. For fast access and availability, a DHCP server should be on the same LAN as or geographically close to the writable partitions the DHCP server uses.
When a DHCP server makes or modifies address assignments, the database is updated. The partition where this database is stored should have at least two writable replicas. Only one replica might be unsafe because of fault tolerance considerations, but three might be too costly in terms of eDirectory performance.