Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Version History

Version 1 Next »

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:

  • Mange 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

There’s an alternative approach to deploying NIOS with BloxOne DDI. BloxOne DDI is configured as primary and NIOS as secondary only. This deployment is followed when a customer wants ADP on NIOS for external authoritative DNS but wants everything managed from the Cloud Services Portal.

  • No labels