Loading

×Sorry to interrupt
Uncaught ReferenceError: addCTracking is not defined
throws at https://kb.vmware.com/resource/KM_TealiumTrackingJS?v=0.5:100:1

Refresh

Cookie Preference Center

General Information on cookies

When you visit our website, we use cookies to ensure that we give you the best experience. This information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies by clicking on the different category headings to find out more and change your settings. However, blocking some types of cookies may impact your experience on the site and the services we are able to offer. Further information can be found in our

Cookie Policy.

Strictly Necessary

Strictly Necessary

Always Active

Strictly Necessary

Strictly necessary cookies are always enabled since they are essential for our website to function. They enable core functionality such as security, network management, and website accessibility. You can set your browser to block or alert you about these cookies, but this may affect how the website functions. For more information please visit www.aboutcookies.org or www.allaboutcookies.org.

Cookie Details‎

Performance

Performance

Performance

Performance cookies are used to analyze the user experience to improve our website by collecting and reporting information on how you use it. They allow us to know which pages are the most and least popular, see how visitors move around the site, optimize our website and make it easier to navigate.

Cookie Details‎

Please confirm your settings by refreshing the page.

Functional

Functional

Functional

Functional cookies help us keep track of your past browsing choices so we can improve usability and customize your experience. These cookies enable the website to remember your preferred settings, language preferences, location and other customizable elements such as font or text size. If you do not allow these cookies, then some or all of these services may not function properly.

Cookie Details‎

Advertising

Advertising

Advertising

Advertising cookies are used to send you relevant advertising and promotional information. They may be set through our site by third parties to build a profile of your interests and show you relevant advertisements on other sites. These cookies do not directly store personal information, but their function is based on uniquely identifying your browser and internet device.

Cookie Details‎

Advertising Cookies

Consent Leg.Interest

Select All Vendors

Select All Vendors

Select All Hosts

Select All

Clear Filters

Information storage and access

Apply

Confirm My Choices Reject All Allow All

My Subscriptions

Loading

Knowledge Base

DNS resolution not working for Windows VMs in VMware Cloud on AWS when VM IP is statically assigned (55695)

Last Updated: 7/6/2018Categories: TroubleshootingTotal Views: 18002Language:
English

1 like this article

Subscribe to get an email
newsletter with new updates

1 people found this helpful Please provide article feedback:

Symptoms

This issue can be observed with Windows VMs in VMware Cloud on AWS who have their IP address statically/manually assigned, and their DNS server IP points to the Compute Gateway DNS Proxy: 169.254.3.1 or to your DNS server directly.

DNS name resolution is not functional for these VMs.

The same issue can affect a windows DNS server running in VMware Cloud on AWS when its IP is statically/manually assigned.  This will cause DNS resolution to fail for ALL VMs in VMware Cloud on AWS using the Compute Gateway DNS Proxy (which is assigned by DHCP when the logical network has DHCP Enabled), as the DNS server will not be able to respond to the Compute Gateway DNS proxy with the DNS results.

Cause

The Compute Gateway uses an IP address from the APIPA IP Range (169.254.3.1) and this IP acts a DNS Proxy for workload VMs when a DNS Server is configured in the Compute Gateway.
Windows Guest VM's don't route APIPA addresses (169.254.x.x) to the default gateway.  That means that when the VM attempts to send traffic to the 169.254.3.1 IP, it is not sent out the network interface.
This works for VMs that are assigned their IP using DHCP, because the Compute Gateway includes a static route for 169.254.3.1 in the DHCP request so that the windows VM knows how to correctly route the traffic.  However, when the VM is configured manually (not using DHCP), this static route does not exist.

Resolution

This is a known issue affecting VMware Cloud on AWS and currently there is no resolution. Refer the workaround section for more details.

Workaround

To workaround this issue, a static route must be manually created so the Windows VM knows how to route traffic to the Compute Gateway DNS Proxy:

Add a Static persistent route in the guest VM using the following command:

route add 169.254.3.1 mask 255.255.255.255 <default GW IP> -p

Where the default GW IP is the GW IP of the network in which the VM resides

e.g. If the VM resides in the 192.168.1.0/24 network, the command will look like the below:
route add 169.254.3.1 mask 255.255.255.255 192.168.1.1 -p

Note: When using the Compute Gateway DNS Proxy for DNS resolution on Guest VMs, firewall rules for DNS do not need to be specifically configured on the Compute Gateway firewall.

However, if you configure your own DNS server directly on a Guest VM, you will need to ensure all firewall rules are opened to allow DNS traffic through Compute Gateway to the DNS servers on TCP and UDP ports 53, with a source IP of the guest VMs and a destination of the DNS server IPs.

e.g. For using Google's public DNS (8.8.8.8 and 8.8.4.4) on a VM (192.168.1.10) you would require a 2 FW rules:

allowing udp port 53 out from 192.168.1.0/24 to 8.8.8.8 and 8.8.4.4

allowing tcp port 53 out from 192.168.1.0/24 to 8.8.8.8 and 8.8.4.4

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

Attachments

Additional Resources

KB
•
End Of General Availability of the Free vSphere Hypervisor (ESXi 7.x and 8.x) (2107518)

KB
•
Download and Install VMware Fusion (2014097)

Results 1-2 of 2

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware Cloud on AWS

Related Versions:

Take Our Survey

Support Assistant