This section explains how to publish NSX Advanced Load Balancer private IP DNS Records to Route 53.

A Virtual Service on an NSX Advanced Load Balancer deployed in an AWS cloud can have two IP addresses:

  • A private IP address, also known as a Virtual IP address (VIP).

  • An external IP address, also known as floating IP address.

When Route 53 is enabled in the AWS cloud, the VIP is registered with the private hosted zone while the floating IP address is registered with the public hosted zone of AWS. The fully qualified domain names (FQDNs) registered in a private hosted zone are reachable only within the cloud’s VPC.

Use Case

The typical use cases of this feature are listed below:

Where the applications reside outside of AWS but need to use Route 53 as a DNS provider.

If there are a large number of AWS VPCs, currently it is required to associate the private hosted zone with every VPC to enable DNS resolution. By enabling this new feature, this tedious configuration is no longer required.

Configurig Route 53

This feature is enabled by setting the publish_vip_public_zone flag (present in the AWS configuration) value to true through the CLI. This feature is available both when the cloud-type is set to AWS, and when the cloud is non-AWS but uses AWS DNS IPAM.

This feature is enabled by setting the publish_vip_public_zone flag (present in the AWS configuration) value to true through the CLI. This feature is available both when the cloud-type is set to AWS, and when the cloud is non-AWS but uses AWS DNS IPAM.

Log in to the NSX Advanced Load Balancer and follow the below steps when the cloud-type is set to AWS:

[admin:<controller-ip>]: > configure cloud <cloud_name>
[admin:<controller-ip>]: cloud> aws_configuration
[admin:<controller-ip>]: cloud:aws_configuration> publish_vip_to_public_zone
[admin:<controller-ip>]: > save

Log in to the NSX Advanced Load Balancer and follow the below steps when AWS DNS is used as a DNS Service:

[admin:<controller-ip>]: > configure ipamdnsproviderprofile <name>
[admin:<controller-ip>]: ipamdnsproviderprofile> aws_profile
[admin:<controller-ip>]: ipamdnsproviderprofile:aws_profile> publish_vip_to_public_zone
[admin:<controller-ip>]: ipamdnsproviderprofile:aws_profile> save
Note:

  • To register the private VIP and the public external IP address (floating IP address), you must have public- and private-hosted zones of the same name, for example, abc.foo.com.

  • To register the private IP address in a public-hosted zone, you must set publish_vip_public_zone, and choose that zone when defining the virtual service.