BloxOne DDI and NIOS Grid Hybrid Deployment

This scenario is a hybrid deployment of BloxOne DDI with NIOS. NIOS Grid Connector uploads IPAM data to BloxOne Cloud. The following diagram illustrates a hybrid deployment of BloxOne DDI with NIOS. In this diagram, NIOS is primary for DNS and BloxOne DDI is secondary:

To manage BloxOne DDI hosts, use the Cloud Services Portal. Start by configuring a DNS Server Group with NIOS as the primary and BloxOne DDI hosts as secondary. Create and assign authoritative zones to this DNS Server Group. Manage DNS data and Grid Members from the NIOS Grid Master, and sync data from the Grid Master (or its candidate) to BloxOne DDI. Alternatively, you can configure BloxOne DDI as the primary and NIOS as secondary, particularly when using ADP on NIOS for external authoritative DNS.

	Manage BloxOne DDI hosts from the Cloud Services Portal.
	Configure DNS Server Group with NIOS as primary and BloxOne DDI hosts as secondary.
	Create auth zones(s) and assign DNS Server Group. Manage DNS data on NIOS Grid Master. Manage Grid Members from the Grid Master.
	Sync data from the Grid Master (or Grid Master Candidate) to BloxOne DDI.

BloxOne DDI is configured as primary and NIOS as secondary only. An alternative deployment is used when you want to configure ADP on NIOS for external authoritative DNS but everything is managed from the Cloud Services Portal.