Shield NS53DNS proxiesCreate a proxyCopy Pagepost https://{hostname}/config-dns/v2/proxiesCreates a new proxy.Query ParamscontractIdstringrequiredThe contract to use for the proxy.gidintegerrequiredThe currently selected group ID to manage.accountSwitchKeystringFor customers who manage more than one account, this runs the operation from another account. The Identity and Access Management API provides a list of available account switch keys.Body ParamsA Proxy.activeHealthcheckobjectActive health check settings for the proxy.activeHealthcheck objectcontractIdstringrequiredThe contract for this proxy.createdTimedate-timeAn ISO 8601 timestamp showing when the proxy was created.ecsSettingbooleanWhether ECS forwarding is enabled for this proxy.truetruefalsefullIpPassthroughEnabledbooleanWhether the full client IP is forwarded in ECS options (/32 for IPv4, /128 for IPv6) rather than a truncated prefix. Requires ecsSetting to be true.truefalsehealthCheckobjectrequiredThe names or addresses of the master name servers to protect.healthCheck objectidstringThe proxy ID.lastModifiedTimedate-timeAn ISO 8601 timestamp showing when the proxy was last modified.namestringrequiredThe proxy name.originNameserverZoneTransferTargetsarray of stringsdeprecatedDeprecated The names or addresses to perform outbound zone transfers for AUTOMATIC filter mode. The default value is the originNameservers section.originNameserverZoneTransferTargetsADD stringoriginNameserversarray of objectsrequiredThe names or addresses of the master name servers to protect.originNameservers*ADD objectzoneTransferNameserversarray of objectsThe names or addresses to perform outbound zone transfers with filter_mode of AUTOMATIC. If this field is omitted the originNameserverZoneTransferTargets section is used.zoneTransferNameserversADD objectHeadersacceptstringenumDefaults to application/jsonGenerated from available response content typesapplication/jsonapplication/problem+jsonAllowed:application/jsonapplication/problem+jsonResponses 201Successful response. 400Bad Request. The request body is missing required data or contains an invalid field value. 401Unauthorized. Your credentials are missing or invalid. 403Forbidden. You don't have permission to create a proxy for the specified contract or group. 409Conflict. The request conflicts with the current state of the proxy. 415Unsupported Media Type. The request's Content-Type header is not supported. Use application/json. 422Unprocessable Entity. The request body contains a semantically invalid field value.Updated 3 months ago List users of a zone's TSIG keyList proxiesDid this page help you?YesNo