Infoblox IPAM Properties

If TRUE, only the host record is created.

If TRUE, the A record is created.

If TRUE, the PTR record which is associated with the A record is created.

If TRUE, the fixed address is created.

If TRUE, the DHCP service in NIOS is automatically restarted if this is required by NIOS configuration.

Enabling this property affects DHCP records: fixed addresses, reservations, and host records with the Enable DHCP option turned on. If you create address and PTR records, enabling this property has no effect.

For a list of operations requiring a DHCP service restart, see xxx

List of aliases for the host record of network interface X in the FQDN format.

DNS view in which the host record or DNS record of network interface X will be created.

The DNS view property should contain DNS zones specified in the DHCP options of networks and ranges selected in the appropriate network profile. If the DNS view is not specified in the property group by default, IPAM Plug-In generates the default DNS view value based on the template "default.<network view>". When the default network view is selected in the network profile or if the network view (the address space in the vRA terminology) is not specified, the default DNS view from NIOS will be used (typically associated with the default network view).

Comment for the record of network interface X.

Enables updating hostnames of appropriate records in NIOS on the “MachineProvisioned” event. You should set this property to TRUE if you use Custom Hostnaming Extension for vRA or alternative solutions for customizing VM names through a vRA extensibility mechanism. Set to TRUE by default.

Infoblox.IPAM.CustomHostname.ConditionalMachine CustomPropertyX.Name

Infoblox.IPAM.CustomHostname.ConditionalMachine CustomPropertyX.Value

These properties take effect only if “Infoblox.IPAM.enableCustomHostname” is set to TRUE. If they are specified, the Plug-In updates the hostname in NIOS only if the property with the same name and value exists in the VM properties list while the VM is spinning up in vRA. It can be useful when you want to skip updating hostname if the initial VM name was not changed by a third-party custom hostnaming extension. You can specify up to three properties to identify the case when the VM name was changed.