EdgeDnsConfig

EdgeDnsConfig
EdgeDnsConfig

Specifies the DNS forwarder configuration for an edge gateway backed by NSX-T.

JSON Example
{
    "enabled": false,
    "listenerIp": "string",
    "defaultForwarderZone": {
        "id": "string",
        "displayName": "string",
        "dnsDomainNames": [
            "string"
        ],
        "upstreamServers": [
            "string"
        ]
    },
    "conditionalForwarderZones": [
        {
            "id": "string",
            "displayName": "string",
            "dnsDomainNames": [
                "string"
            ],
            "upstreamServers": [
                "string"
            ]
        }
    ],
    "version": {
        "version": 0
    },
    "snatRuleExternalIpAddress": "string",
    "snatRuleEnabled": false
}
boolean
enabled
Optional

True means that the forwarder is enabled. False means it's disabled.

string
listenerIp
Optional

The IP on which the DNS forwarder listens. If the Edge Gateway has a dedicated external network, this can be changed.

defaultForwarderZone
Optional

defaultForwarderZone

conditionalForwarderZones
Optional

The list of forwarder zones with its matching DNS domains.

version
Optional

version

string
snatRuleExternalIpAddress
Optional

The external IP address of the SNAT rule. This property only applies if the Edge Gateway is connected to a Provider Gateway using IP Space. If specified, VCD will conveniently manage the SNAT rule with the specified IP address for the DNS forwarder. In NAT routed environments, an SNAT rule is required for the Edge DNS forwarder to send the traffic to an upstream server. In fully routed environments, this is not needed if the listener IP is on an advertised subnet. If unset, the VCD-managed NAT rules will be removed and users can choose to manually manage the NAT rules.

boolean
snatRuleEnabled
Optional

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 is connected to a dedicated Provider Gateway 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.

Availability
Added in 32.0