6.5.1

Table Of Contents
DNS and routing details about the selected TCP/IP stack appear below the TCP/IP Stacks table. You can
view the IPv4 and IPv6 routing tables, and the DNS and routing configuration for the stack.
Note The IPv6 routing table is only visible if IPv6 is enabled on the host.
The Advanced tab contains information about the configured congestion control algorithm and the
maximum number of allowed connections to the stack.
Change the Configuration of a TCP/IP Stack on a Host
You can change the DNS and default gateway configuration of a TCP/IP stack on a host. You can also
change the congestion control algorithm, the maximum number of connections, and the name of custom
TCP/IP stacks.
Note You can change the DNS and default gateway configuration of the default TCP/IP stack only.
Changing the DNS and default gateway configuration of custom TCP/IP stacks is not supported.
Procedure
1 In the vSphere Web Client, navigate to the host.
2 On the Configure tab, expand Networking and select TCP/IP configuration.
3 Select a stack from the table, click Edit and make the appropriate changes.
Page Option
Name Change the name of a custom TCP/IP stack
DNS Configuration Select a method of obtaining the DNS server.
n
Select Obtain settings automatically from a VMkernel network adapter and select a network
adapter from the VMKernel network adapter drop-down menu
n
Select Enter settings manually and edit the DNS configuration settings.
a Edit the Host name.
b Edit the Domain name.
c Type a preferred DNS server IP address.
d Type an alternate DNS server IP address.
e (Optional) Use the Search domains text box to specify DNS suffixes to use in DNS search when
resolving unqualified domain names.
Routing Edit the VMkernel gateway information.
Note Removing the default gateway might cause the client to lose connectivity with the host.
Advanced Edit the maximum number of connections and the congestion control algorithm of the stack
4 Click OK to apply your changes.
What to do next
You can add static routes to additional gateways by using CLI commands. For more information, see
http://kb.vmware.com/kb/2001426
vSphere Networking
VMware, Inc. 71