DHCP Range

This resource ties to the network resource, enabling the network for DHCP is not enough to have it serve dhcp requests, we need to set this resource to determine the range of its that the network should serve.

Example usage

resource "infoblox_dhcp_range" "ExampleRange" {
        name = "my new network range extended"
        comment = "this is a comment updated"
        network = "10.10.10.0/24"
        network_view = "default"
        start = "10.10.10.20"
        end = "10.10.10.45"
        member = {
                ipv4_addr = "10.93.58.10"
                name  = "s1ins01.devops.int.ovp.bskyb.com"
        }
        server_association = "MEMBER"
}

Argument reference :

The following arguments are supported

• name - (Optional) (String) - A name describing the DHCP Range

• comment - (Optional) (String) - Comment field

• network - (Required) (String) - The infoblox network that we are creating the range in. This should be the CIDR notation describing the network (see example)

• network_view- (Required) (String) - The network view that we are creating this range under

• start - (Required) (String) - The start for the ip range

• end - (Required) (String) - The end for the ip range

• member - (optional) (Schema) - The infoblox grid member that is supposed to serve this range, the reason this is optional is that we could create a range in order to reserve the ip space, the member schema has the following fields

  • ipv4_addr - (Optional) (String) - IP address of the member server
  • name - (Optional) (String) - FQDN of the member server, it needs to match what's defined in the infoblox grid

• restart - (Optional) (Boolean) - Should the infoblox services be restarted on create/update

• server_association - Optional) (String) - How the server/range association is done, Must be set to MEMBER if the member parameter is set.