/
Configuring NIOS-X as a Service
Document toolboxDocument toolbox

Configuring NIOS-X as a Service

Owned by Sri Raghu
Last updated: Jan 22, 2025 by Shirly Tsang
2 min read

Infoblox has expanded its DNS and DHCP capabilities beyond the traditional on-premises server deployment at each location. NIOS-X as a Service now offers a seamless deployment experience that eliminates the need for deployment of servers on-site. This innovative approach allows your local devices 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:

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

    • Access Location: This is the remote site where the service is used. For example, it can be a physical site (such as a branch office), a data center, or a Virtual Private Cloud. An access location may contain multiple WAN IP addresses and VPN connections. Each WAN IP address can support up to two VPN tunnels.

    • Service Location: This is where the service is hosted. For example, AWS US East (N. Virginia) or GCP US West (Oregon). 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.

When assigning DNS Zones from multiple views to the same NIOS-X as a Service configuration, it is essential that all DNS views include match-client ACLs. Failing to do so may result in the DNS server randomly serving zones from only one of the views.

The following diagram explains NIOS-X as a Service:


List of topics: