This section discusses the native IPAM and DNS support for the various clouds.

Provider

Infoblox

NSX Advanced Load Balancer

Internal

Cloud-native

Cloud Infrastructure

IPAM

DNS

IPAM

DNS

IPAM

DNS

VMware vCenter

Yes

Yes

Yes

Yes

NA

NA (Not Used)

No access cloud

Yes

Yes

Yes

Yes

Yes

No

  • When creating virtual services in OpenStack or AWS cloud, a separate configuration for IPAM is not needed/allowed, since the cloud configuration has support for IPAM natively in NSX Advanced Load Balancer.

    • When you select 'Default', the cloud’s IPAM/DNS support is accepted without additional action on the part of the administrator.

    • NSX Advanced Load Balancer supports Route 53 when AWS is the configured cloud provider.

    • Although the cloud supports DNS, 'Not Used' means NSX Advanced Load Balancer does not use it.

  • When creating a virtual service in the Linux Server cloud in AWS/GCP environment, you can use the cloud-native IPAM solution of AWS/GCP.

  • NSX Advanced Load Balancer DNS service can be used with all these clouds.

IPAM and DNS Provider (Infoblox)

The Controller integrates with Infoblox’s RESTful Web API (WAPI) for IPAM and DNS services.

These API calls are initiated by the Controller and directed to the Infoblox Grid Master IP address, or virtual IP address (VIP), if it has been deployed in a HA pair. This integration enables the NSX Advanced Load Balancer to automate the allocation of IP addresses as well as the creation and deletion of host objects in DNS as new virtual services are created/deleted in the NSX Advanced Load Balancer environment.

Ensure that all interested subnets and domain names (zones) have been configured in the Infoblox server for consumption by NSX Advanced Load Balancer.

Infoblox IPAM and DNS profiles should be independently defined and configured. For a given cloud, the permitted Infoblox combinations are:

IPAM Provider

DNS Provider

Infoblox IPAM

None, Infoblox DNS, NSX Advanced Load Balancer internal

Any

Infoblox DNS