Create Dhcp Binding

Create Dhcp Binding

Creates a DHCP binding on an Org vDC Network.

Request
URI
POST
https://{api_host}/cloudapi/1.0.0/orgVdcNetworks/{vdcNetworkId}/dhcp/bindings
COPY
Path Parameters
string
vdcNetworkId
Required

vdcNetworkId

string
vdcNetworkId
Required

vdcNetworkId


Request Body
DhcpBinding of type(s) application/json
Optional
{
    "id": "string",
    "name": "string",
    "description": "string",
    "macAddress": "string",
    "ipAddress": "string",
    "leaseTime": 0,
    "dnsServers": [
        "string"
    ],
    "bindingType": "string",
    "dhcpV4BindingConfig": {
        "gatewayIpAddress": "string",
        "hostName": "string"
    },
    "dhcpV6BindingConfig": {
        "sntpServers": [
            "string"
        ],
        "domainNames": [
            "string"
        ]
    },
    "version": {
        "version": 0
    }
}
string
id
Optional

The unique id of the DHCP binding.

string
name
Required

Display name for the DHCP binding.

string
description
Optional

Description for the DHCP binding.

string
macAddress
Required

MAC address of the host.

string
ipAddress
Optional

IP Address assigned to host. This address must belong to the subnet of Org vDC network. For IPv4, this is required. For IPv6, when not specified, Stateless Address Autoconfiguration (SLAAC) is used to auto-assign an IPv6 address to the DHCPv6 clients.

integer As int64 As int64
leaseTime
Optional

The amount of time in seconds of how long a DHCP IP will be leased out for. The minimum is 60s while the maximum is 4,294,967,295s, which is roughly 49,710 days. Default is 24 hours.

array of string
dnsServers
Optional

DNS nameservers to be set to client host.

string
bindingType
Required

The type of DHCP binding.

  • IPV4 - an IPv4 DHCP binding.
  • IPV6 - an IPv6 DHCP binding.
dhcpV4BindingConfig
Optional

dhcpV4BindingConfig

dhcpV6BindingConfig
Optional

dhcpV6BindingConfig

version
Optional

version

Authentication
This operation uses the following authentication methods.
Responses
202

The request have been accepted and the task to monitor the request is in the Location header.

Operation doesn't return any data structure