SNAT and NO DNAT rules for DNS are not automatically created when configuring DNS Forwarder Service on an Edge Gateway
Article ID: 385131
Updated On:
Products
Issue/Introduction
- Configuring a DNS Forwarder Service on an Edge Gateway under IP Management > DNS in the Cloud Director Provider or Tenant portal.
- When the Listener IP > Use Default option is disabled and a non-default IP Address value is entered, SNAT and NO DNAT rules for DNS are NOT automatically created on the Edge Gateway under Services > NAT.
- When the Listener IP > Use Default option is enabled, SNAT and NO DNAT rules for DNS are automatically created on the Edge Gateway under Services > NAT.
Environment
VMware Cloud Director 10.6.x
Cause
This is expected behaviour in Cloud Director when a non-default IP Address is used for the Listener IP.
If a default Listener IP Address is used then the NAT rules are automatically created, otherwise Cloud Director does not create or removes the NAT rules.
The expectation for a non-default Listener IP Address is that the NAT rules will also be manually created by the user or that no NAT rules are needed as the Listener IP Address is on an advertised subnet in a fully routed environment.
Resolution
In scenarios where the Listener IP > Use Default option is disabled and a non-default IP Address is used then the user should either manually created the required NAT rules or ensure that the custom Listener IP is on an advertised subnet in a fully routed environment where the NAT rules would not be needed.
Additional Information
Feedback
