Update Edge Gateway DNS
DescriptionUpdates DNS configuration of the edge gateway.
Request
URLURL
Path Parameters
Path Parameters
Request Body
{
"conditionalForwarderZones": [
{
"displayName": "string",
"dnsDomainNames": [
"string"
],
"id": "string",
"upstreamServers": [
"string"
]
}
],
"defaultForwarderZone": {
"displayName": "string",
"dnsDomainNames": [
"string"
],
"id": "string",
"upstreamServers": [
"string"
]
},
"enabled": false,
"listenerIp": "string",
"snatRuleEnabled": false,
"version": {
"version": 0
}
}
The list of forwarder zones with its matching DNS domains.
The default forwarder zone to use if there’s no matching domain in the conditional forwarder zone.
True means that the forwarder is enabled. False means it’s disabled.
The IP on which the DNS forwarder listens. If the Edge Gateway has a dedicated external network, this can be changed.
Whether there is an SNAT rule exists for the DNS forwarder or not. In NAT routed environments, an SNAT rule is required for the Edge DNS forwarder to send traffic to an upstream server. In fully routed environments, this is not needed if the listener IP is on an advertised subnet. If the Edge Gateway has a dedicated external network and the listener IP has been changed, there will not be an SNAT rule for the DNS forwarder. In all other cases the SNAT rule will exist.
This property describes the current version of the entity. To prevent clients from overwriting each other’s changes, update operations must include the version which can be obtained by issuing a GET operation. If the version number on an update call is missing, the operation will be rejected. This is only needed on update calls.
Authentication
Errors
Invalid configuration.
The specified resource was not found
