Page Comparison

BloxOne DDI Infoblox has expanded its DNS and DHCP capabilities beyond the traditional on-premises host server deployment at each location. BloxOne DDI NIOS-X as a Service now offers a seamless installation deployment experience that eliminates the need for an onsite hostdeployment of servers on-site. This innovative approach allows your local devices or AWS instances to establish direct communication with the Cloud Services Portal without any additional intermediary hardware. Experience streamlined operations and simplified management with BloxOne DDI as a Service, connecting you directly to our cloud-based solutions.

BloxOne DDI as a Service can be configured as follows:

• Customer devices in various locations can seamlessly interact with BloxOne DDI Service Endpoint by configuring their routers that facilitate Internet access.

The following diagram explains BloxOne DDI to use DNS and DHCP services from the Infoblox cloud without deploying any physical or virtual servers.

NIOS-X as a Service can be configured by establishing site-to-site IPsec VPN tunnels from your on-prem devices (for example, router, firewall, SD-WAN appliance, etc) to the appropriate NIOS-X as a Service endpoints in the cloud. DNS and/or DHCP traffic can then be routed through the VPN tunnels to Infoblox run cloud services.

NIOS-X as a Service consists of the following:

• Service: A Service is a container object for capability and service deployment. It can have multiple capabilities with different service deployment configurations.

• Capability: Capability is a feature that is enabled on the Infoblox-managed cloud. They are DNS, DHCP, and Security. For each of these capabilities, you can associate a configuration. This can be the Global Policy (default) or a custom policy. For more information, see:

  • DNS Config Profile

  • DHCP Config Profile

  • Creating a Security Policy (DNS Forwarding Proxy)

• Service Deployment: A service deployment consists of the following:

  • Access Location: This is where the service is used. For example, it can be a physical site (branch office), a data center, or a Virtual Private Cloud.

  • Service Location: This is where the service is hosted. For example, AWS US (N. Virginia) or GCP ASE (Singapore). NIOS-X as a Service supports many service locations in AWS and GCP.

• Service Insights: A graphical representation of various parameters that provides a snapshot at a glance.

The following diagram explains NIOS-X as a Service:

BloxOne DDI as a Service can be deployed as follows:

1. Create a Location: Create a location for each branch office. For more information, see Configuring a Location.

2. Create a Managed Endpoint: Create a Managed Endpoint for each type of deployment. For more information, see Creating a Managed Endpoint.

3. Associate locations with Managed Endpoints: Choose the Locations that will be managed by the Managed Endpoints. For more information, see Creating a Managed Endpoint.

4. Integrate the Pre-shared Key (PSK) generated from BloxOne DDI into your local router to establish a connection with BloxOne DDI via your router. This PSK can be added to any router that you are utilizing for internet connectivity. Should your router already contain a pre-shared key, it is possible to incorporate this existing key within BloxOne DDI.

   • For more information on adding an existing pre-shared key, see Configuring a Location.

   • For more information on adding a pre-shared key generated in BloxOne DDI into your router, refer to the documentation for your router.

You can perform the following actions:

List of topics: