- United States
- United Kingdom
IPv6: How to configure static and DHCP IP addressing and deal with DNS
Ipv6 offers several ways that aren’t possible in ipv4 to assign ip addresses, and dns set-up has differences as well..
Network World |
As IP technology has matured, the range of devices that the internet protocol supports goes well beyond computers to include cell phones, entertainment systems, and Internet of Things (IoT) devices, which created the need for more IP addresses and the development of IPv6 to provide them.
With more and more device types requiring network connectivity, the demand for addresses in an IPv4-based network is at a premium. It can provide somewhere south of 4,294,967,296 unique addresses. IPv6 , on the other hand, can yield roughly 3.4×10 38 , which should be ample for a very long time.
IPv6 also includes performance enhancements like refined multicasting, stateless address autoconfiguration (SLAAC), simplified headers to streamline router processing, and the option to allow larger packets. Security also gets a potential boost in IPv6 with IPSec, which was initially built for IPv6 and then retrofitted for IPv4.
Dealing with IPv6 includes familiarizing yourself with two important IP concepts: DHCP and DNS. Here are tips on both.
Key IPv6 addressing concepts
IPv6 addressing within a network has a few major differences from IPv4. With IPv4 certain address ranges are reserved for private networks (such as 10.0.0.0/8 or 192.168.0.0/16) and link-local addressing without dynamic host configuration protocol (DHCP) (169.254.0.0/16).
DHCP automatically assigns IP addresses and distributes other information to hosts on a network so they can communicate with other endpoints. At the same time, by assigning active IP addresses only to active devices, DHCP can reuse them to help conserve IPv4 addresses. IPv6 has similar concepts but refines each idea a little further.
Link-local addresses in IPv6 exist on each interface, regardless of whether the interface has an address assigned from DHCP or is configured using another method. Link-local IPv6 addresses have a prefix of fe80::/10 and a 64-bit suffix which can be computed and managed by the host itself without requiring additional networking components. IPv6 hosts can verify the uniqueness of their link-local addresses through a neighbor discovery process, which reaches out to the local network in order to verify that the address is not already in use.
Once a link-local address has been established, the IPv6 host attempts to determine if an IPv6-capable router is available through the use of a router solicitation message. If an IPv6 router is available it will respond with a router advertisement, which includes network configuration information such as a network prefix that is used for automatic address configuration using SLAAC or whether the host should obtain additional configuration information from a DHCPv6 server.
Configuring a Static IPv6 address in Windows
Typical to Windows, there are three ways to configure a static IPv6 address for a network adapter, all of which work in Windows 10 and in both Windows Server 2016 and 2019. The first way uses the classic Control Panel method as follows.
From the Control Panel, navigate to Network and Internet, Network and Sharing Center, and then choose the Change adapter settings link in the left panel. (You can shortcut all the clicking by searching for “View Network Connections” from the Start Menu or the Search bar).
Once you locate the network adapter you wish to configure, you can view the properties and locate the Internet Protocol Version 6 (TCP/IPv6) node and configure the properties for the IPv6 protocol. As with IPv4 you can set the adapter to obtain the IPv6 address automatically or configure your own IPv6 address, subnet, default gateway, and DNS server information. If you need to set multiple IPv6 addresses this can be accomplished by clicking the Advanced button.
The second method of setting a static IP address involves the more modern Settings application. In Settings go to Network & Internet and click the Properties button for the interface you wish to configure. Click the Edit button under IP settings, change the configuration type to Manual, enable IPv6, and populate your settings.
The third way is to use the Windows PowerShell command-line interface. In order to set a static IPv6 address using the New-NetIPAddress cmdlet you will need either the name or the numeric index of the adapter you wish to configure. Both of these values are available using the Get-NetAdapter cmdlet. From an administrative PowerShell prompt enter one of the following commands (on a single line) replacing the details as necessary for your environment:
Managing IPv6 Addressing for a Windows Network
Static IP addresses are generally OK to use when the device is hosting a critical network service that requires retaining a consistent network address, but for general use you’ll want to have a way to automate address configuration.
In an IPv4 network DHCP is the obvious answer for IP configuration and can also provide critical networking details such as the default gateway or DNS-server addresses through DHCP options. IPv6 offers three potential scenarios for managing addressing and network configuration.
SLAAC is a straightforward option assuming your router supports the appropriate router-advertisement messages. DHCP is certainly still in play to handle stateful addressing in the form of DHCPv6. You can also potentially have a hybrid scenario where your router handles addressing, and DHCPv6 simply provides the relevant network-configuration details.
In Windows Server 2016 and 2019, configuring DHCPv6 is extremely straightforward. If your router is configured to handle router advertisements and addressing through SLAAC you can simply manage the IPv6 server options to configure DNS servers or other options. If you prefer to roll with stateful addressing you can add one or more DHCPv6 scopes and configure a prefix, any exclusions, and lease durations. DHCPv6 scopes will maintain a list of leases and their expirations just as an IPv4 scope would, and they also provide an easy path for creating IPv6 reservations from existing leases.
Setting up DNS Name Resolution for IPv6
DNS is incredibly important in an IPv6 network, even moreso than in an IPv4 network because trying to configure connectivity and access resources using only IPv6 addresses is borderline insane. The biggest difference to note in regard to using DNS with IPv6 is that the IPv4 A records, which convert a fully qualified domain name (FQDN) to an IPv4 address, are replaced by AAAA (quad-A) records. All other record types such as CNAME, MX, NS, SOA, and the various DNSSEC-related record types simply reference the FQDN of the AAAA record. Reverse lookup zones, which are used to find a hostname from an IP address, are different in IPv6 simply because they are built on the IP address structure, but the process of creating and using these zones are functionally identical.
The DNS server role in Windows Server supports both IPv4 and IPv6 through a similar set of tools and processes. As with A records, AAAA records can either be created manually for critical systems or the dynamic update process can be leveraged to manage DNS records for the entire enterprise.
AAAA records can be manually created using the DNS console through the same process as A records: Right click the required DNS zone, select the New Host (A or AAAA) option, and populate the Host name and IP address. Dynamic updates are enabled through the DNS console, but most of the work is done by DHCP; the update process is configured within the DHCP console and updates are performed by the DHCP client service on individual hosts. Dynamic updates can also be manually initiated from the command line using the ipconfig command with the /registerdns switch.
- 9 career-boosting Wi-Fi certifications
- What is MPLS, and why isn't it dead yet?
- 11 ways to list and sort files on Linux
- 5 free network-vulnerability scanners
- How-to measure enterprise Wi-Fi speeds
Tim Ferrill is an IT professional and writer living in Southern California, with a focus on Windows, Windows Phone, and Windows Server.
Copyright © 2021 IDG Communications, Inc.
- Portal Home
How to configure IPv6 in Windows
(QuickPacket supports IPv6! Get a server from us with promo code PACKETS for 15% off your first invoice)
Internet Protocol version 6 (IPv6) is the latest version of the Internet Protocol (IP) intended to replace IPv4, which still carries more than 96% of the worldâ€™s Internet traffic as of May 2014. This article discusses how you can adapt and configure IPv6 in your Windows machines.
The 128 bits of an IPv6 address are represented in 8 groups of 16 bits each. Each group is written as 4 hexadecimal digits and the groups are separated by colons (:).
An IPv6 address may be abbreviated to shorter notations by using the following rules where possible:
- One or more leading zeroes from any group of hexadecimal digits are removed.
- Consecutive sections of zeroes are replaced with a double colon (::), which can only be used once in an address, as multiple uses would render the address indeterminate. RFC 5952 (http://tools.ietf.org/html/rfc5952) recommends that a double colon must not be used to denote an omitted single section of zeroes.
See below for applications of these rules:
Initial address Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â 2001:0db8:0000:0000:0000:ff00:0042:8329
After removing all leading zeroes Â Â Â Â Â Â Â Â Â 2001:db8:0:0:0:ff00:42:8329
After omitting consecutive sections of zeroes Â Â 2001:db8::ff00:42:8329
The loopback address â€œ0000:0000:0000:0000:0000:0000:0000:0001â€ may be abbreviated to â€œ::1â€ by using both rules.
As an IPv6 address may have more than one representation, the Internet Engineering Task Force (IETF) has issued a proposed standard for representing them as text .
IPv6 Address Scopes
Â The following points cover the scopes of an IPv6 address.
Global Unicast address. Â IPv6â€™s Global Unicast address is equivalent to anÂ IPv4 Public address. Its scope is the entire IPv6 Internet, so it is globally routable and reachable on the IPv6 Internet. To enable greater efficiency in the routing architecture, Unicast addresses are designed to be aggregated.
- Global Routing Prefix (part of the Public Routing Topologyâ€”along with 001 prefix)
- Subnet ID (Site Topology)
- Interface ID
Link-local address. An IPv6 Unicast Link-local address is similar toÂ the IPv4 APIPA addressÂ used by machines running MicrosoftÂ® WindowsÂ®. It enables hosts on the same subnet to communicate with each other. It is always automatically configured even without all other unicast addresses.
- FE80::/64 prefix
- Single subnet, router-less configuration
- Used for some Neighbor-discovery process
- Compared to routable addresses, link-local addresses are ambiguous so Zone IDs are used to identify specific interfaces
- Windows Vista and above display the IPv6 Zone ID of local addresses in the ipconfig output
Â Unique Local/Site-local address (ULA). Site-local addresses provide a private addressing alternative to global addresses for intranet traffic. It can be reused to address multiple sites within an organization as a site local address prefix can be duplicated.
- RFC 4193 define this unique local address
- Equivalent to IPv4 Private address
- FD00::/8 prefix
- Replacement for site-local addresses
- Global scope; no Zone ID required
IMPORTANT: The IPv6 addressing architecture requires all subnets using Globally Unique addresses and ULAs to always have 64-bit prefix lengths. Any subnet prefix length other than 64-bit breaks many features of IPv6.
Â Decide whether you will use public IPv6 addresses that are globally aggregatable or if you will use a private address space. In using public IPv6 addresses, you would need to get an IPv6 address prefix from your ISP. If your ISP does not support IPv6 yet, you can get an address prefix from a tunnel broker .
If you want to use private IPv6 addresses, use locally unique addresses. Do note however that most operating systems and applications still support site-local addresses, which are officially deprecated. This means that you need to get a unique prefix. There are already a growing number of sites that generate locally unique address prefixes like SixXS or Unique Local IPv6 Generator . You can use private addresses in the interim to immediately provide IPv6 connectivity in your intranet then move on to public IPv6 addresses later .
Do not forget to check if your Microsoft product supports IPv6. Go here to read Microsoftâ€™s official list .
Â Auto-configuration in Windows
Â IPv6 can configure itself even without the use of DHCP. It is installed and enabled by default in the following Microsoft products:
- Windows Server 2012
- Windows Server 2008 R2
- Windows Server 2008
- Windows Vista
IPv6 for Windows is also designed to auto-configure itself. It automatically sets up link-local addresses for communication between nodes on a link. Moreover, if there is an Intra-Site Automatic Tunnel Addressing Protocol (ISATAP) router or an IPv6 router on the hostâ€™s subnet, the host uses received router advertisements to automatically configure additional addresses, a default router, and other setup parameters.
Â Note that IPv6 is not installed in Windows XP and Windows Server 2003 systems.
Configuration in IPv6-ready Network Systems
Â For Windows 8 and Server 2012, if you already have an unconfigured but IPv6-ready network infrastructure, you can still use IPv6 and configure IPv6 addresses in these situations:
- For home users with public IP addresses, Windows will try to establish a connection using the IPv6 transition technology Teredo . Teredo will work only if the Windows machine is not joined to a domain and has UDP access to the Internet, with no firewall-blocking packets.
- If Teredo fails for home users with public IP addresses, Windows will use another IPv6 transition technology named 6to4 , which requires only a publicly routable IP address.
- Windows can resolve the name of your network using ISATAP through DNS or name broadcasts. In this situation, Windows will assume that the host is an ISATAP server capable of accepting IPv6 packets encapsulated in IPv4 packets. It will then deliver these packets to IPv6 hosts, encapsulate the replies, and send those replies back. ISATAP works in domain-joined, non-domain-joined, and non-routable IP address environments.
Â You can manually configure IPv6 addresses and other parameters in Windows by using the following tools:
- Properties of TCP/IPv6 component
You can configure basic IPv6 settings through the properties of the TCP/IPv6 component.
The following instructions are to statically address Windows 2008 and Windows 2008 R2 servers:
- Log on to the server with administrator rights.
- Go to Start > Network > Network and Sharing Center > Change Adapter Setting.
- Right-click on the Local Area Connection of the network adapter and choose â€œI want to set IPv6.â€ Click on Properties.
- Pick TCP/IPv6 and click on Properties.
- Click â€œUse the following IPv6 addressâ€ and in the IPv6 address field, type the IP address you want to use.
6. Press the Tab key and the subnet prefix length will automatically populate with 64. 7. Press the Tab key again and in the Default Gateway field, type the IP address you want to use for your gateway.
Â Â Â Â Â Â Â Â Â Â Â Â Â Â Example
8. In the Preferred DNS Server field, type the IP address of your DNS server
if your IP address sits on your DNS server: fda8:06c3:ce53:a890:0000:0000:0000:0001
9. Click OK. Close to save and exit.
- Windows PowerShell
In Windows Server 2012 and Windows 8, you can configure IPv6 addresses, default gateways, and DNS servers at the Windows PowerShell command prompt. You can use the following PowerShell cmdlets:
To configure IPv6 addresses, you can use the New-NetIPAddress cmdlet. Â Â Â Â Â Â Example
To configure the IPv6 Unicast address 2001:db8:290c:1291::1 on the interface named â€œWired Ethernet Connection,â€ use the following command:
New-NetIPAddress â€“InterfaceAlias "Wired Ethernet Connection" â€“IPAddress 2001:db8:290c:1291::1
Adding Default Gateways
To configure a default gateway, you can use the New-NetRoute Windows PowerShell cmdlet.
To add a default route that uses the interface named â€œWired Ethernet Connectionâ€ with a next-hop address of fe80::2aa:ff:fe9a:21b8, use the following command:
New-NetRoute â€“DestinationPrefix ::/0 â€“InterfaceAlias "Wired Ethernet Connection" â€“NextHop fe80::2aa:ff:fe9a:21b8
Adding DNS Servers
To configure the IPv6 addresses of DNS servers, you can use the Set-DnsClientServerAddress Windows PowerShell cmdlet.
Example To add a DNS server with the IPv6 address 2001:db8:99:4acd::8 that uses the interface named â€œWired Ethernet Connection,â€ use the following command:
Set-DnsClientServerAddress -InterfaceAlias "Wired Ethernet Connection" -ServerAddresses 2001:db8:99:4acd::8
Â Use these Windows PowerShell commands to display information about the IPv6 configuration of a computer:
- Get-NetIPInterface -AddressFamily IPv6
- Get-NetIPAddress -AddressFamily IPv6
- Get-NetRoute -AddressFamily IPv6
- Get-NetNeighbor -AddressFamily IPv6
- Netsh.exe tool
You can configure IPv6 settings from the interface of IPv6 context of the Netsh.exe tool. You can also configure IPv6 addresses, default gateways, and DNS servers at the command line by using commands in the "netsh interface ipv6" context.
Configuring IPv6 addresses Use the "netsh interface ipv6 add address" command with the following syntax:
netsh interface ipv6 add address [interface=]InterfaceNameorIndex[address=]IPv6Address[/PrefixLength] [[type=]unicast|anycast] [[validlifetime=]Time|infinite] [[preferredlifetime=]Time|infinite] [[store=]active|persistent]
Example To configure with infinite valid and preferred lifetimes the IPv6 unicast address 2001:db8:290c:1291::1 on the interface named â€œLocal Area Connectionâ€ and make the address persistent, use the following command:
netsh interface ipv6 add address "Local Area Connection" 2001:db8:290c:1291::1
Use the "netsh interface ipv6 add route" command and add a default route (::/0) with the following syntax:
netsh interface ipv6 add route [prefix=]::/0 [interface=]InterfaceNameorIndex [[nexthop=]IPv6Address] [[siteprefixlength=]Length] [[metric=]MetricValue] [[publish=]no|yes|immortal] [[validlifetime=]Time|infinite] [[preferredlifetime=]Time|infinite] [[store=]active|persistent]
To add a default route that uses the interface named â€œLocal Area Connectionâ€ with a next-hop address of fe80::2aa:ff:fe9a:21b8, use the following command:
netsh interface ipv6 add route ::/0 "Local Area Connection" fe80::2aa:ff:fe9a:21b8
To configure the IPv6 addresses of DNS servers, use the "netsh interface ipv6 add dnsserver" command with the following syntax:
netsh interface ipv6 add dnsserver [name=]InterfaceName[[address=]IPv6Address] [[index=]PreferenceValue]
By default, the DNS server is added to the end of the list of DNS servers. If an index is specified, the DNS server is placed in that position in the list and the other DNS servers are moved down the list.
Example To add a DNS server with the IPv6 address 2001:db8:99:4acd::8 that uses the interface named â€œLocal Area Connection,â€ use the following command:
netsh interface ipv6 add dnsserver "Local Area Connection" 2001:db8:99:4acd::8
You can obtain IPv6 configuration information with the following commands in the "netsh interface ipv6" context of the Netsh tool:
- netsh interface ipv6 show address
- netsh interface ipv6 show interface
- netsh interface ipv6 show route
- netsh interface ipv6 show neighbors
Note that you can also view IPv6 addresses and routes using the Ipconfig.exe and Route.exe tools (i.e. ipconfig and route print -6 commands).
Though you cannot remove IPv6 support from Windows Vista to Server 2012 R2, you can disable it. You can also just unbind IPv6 from the physical adapters. This will mean however, that IPv6 will still be running and can still be used to connect to IPv6 sites over IPv4. Read the Microsoft Support article " How to disable IP version 6 or its specific components in Windows " for more details.
Connectivity Testing and Troubleshooting
Windows includes the following IPv6-enabled command-line tools that you can use for network troubleshooting:
To ping an IPv6 address, use the syntax: ping IPv6Address [%ZoneID] . Note that the zone ID is not needed when the destination is a global address.
To send ICMPv6 Echo Request messages to the link-local address fe80::260:97ff:fe02:6ea5 using zone ID 4 (the interface index of an installed Ethernet adapter), use the following command:
This ping command includes the -6 flag, which forces Ping to use IPv6. If all is well, you should see a reply, which should be quite fast especially if you have a native IPv6 connection to the Internet. If your echo request does not get a reply, there might be a firewall or networking device blocking ICMPv6 between your Windows system and the target.
Once you know you have connectivity to the Internet using IPv6, be sure to test some IPv6-only websites to verify that everything is working properly.
A DNS lookup for the host ipv6.google.com
Name:Â Â Â ipv6.l.google.com
- 54 Users Found This Useful
(Is your server's network not living up to its potential? Order a server from us with promo code...
(Is your server not living up to its potential? Order a server from us with promo code PACKETS...
A humble company with the heart of a small business, and the staffing of a large one. We are able to meet your needs with personalized, always available support.
Stack Exchange Network
Stack Exchange network consists of 181 Q&A communities including Stack Overflow , the largest, most trusted online community for developers to learn, share their knowledge, and build their careers.
Super User is a question and answer site for computer enthusiasts and power users. It only takes a minute to sign up.
Q&A for work
Connect and share knowledge within a single location that is structured and easy to search.
How can I figure out what IPv6 to use if I want to set a static IP for my computer?
I recently installed Windows Server 2012 on my desktop. I changed my connection settings to hardcode my internal IP address as 192.168.0.99 (IPv4). Windows Server 2012 warned me that I should also set my IPv6 address to a static address, but I'm not sure what the equivalent address is in IPv6 format. I've attempted to google this, however after visiting a few websites that "convert IPv4 to IPv6" they each give me different values. I'm not sure which one is the correct one.
How does one go about translating an IPv4 address to and IPv6 address appropriately? Specifically, I'd like to know what 192.168.0.99 is in IPv6 format. Thanks!
- Tell your OS to use unique local addresses. These are the real replacement for private addresses. They cannot be fixed, because they have to be unique even when LAN are merged, but under normal condition, they should stay the same if there is no conflict. – BatchyX Jan 5, 2013 at 13:28
- 2 the 192.168.*.* * (reusable/unrouted addresses) addresses are a work around for ipv4 to be able to continue to work while running out of address space. ipv6 is the solution. – ctrl-alt-delor Jan 5, 2013 at 14:25
5 Answers 5
IPv6 has an equivalent of IPv4 "private range" addresses – called Unique Local Address ( RFC 4193 ) – it uses the fd00::/8 range. Pick a random /48 or /64 prefix within that range (see Wikipedia article for examples) and use it for your network.
A direct translation of your internal IPv4 addresses wouldn't make much sense, however. (If you did that, you'd also have the same limits as with IPv4, don't you think?)
However, with IPv6 it is not necessary to use local addresses. There are several ways you can get a global address range for yourself, even if your ISP doesn't offer native IPv6 yet:
You can sign up at Tunnelbroker or similar services; most of them will give you a globally-reachable /64 block – that's one subnet – and many will even provide /48 or /56 blocks upon request (64k and 256 subnets respectively). The same tunnel also lets you access the global IPv6 internet.
Or you can use the 6to4 address range based on your global IP address. For example, if your ISP assigns you 18.104.22.168 (C0 00 7B EA in hexadecimal), then you're allowed to use 2002:c000:7bea::/48 . Such addresses are reachable from the Internet as well.
- Good advise. If you want to run IPv6 on your LAN this is the way to do it. – Sander Steffann Jan 6, 2013 at 14:23
To expand grawity's answer (the equivalent to private ranges are Unique Local Addresses, RFC 4913), here is how to pick the actual address to use.
With IPv4 private ranges like 192.168.X. , you randomly pick the value for X, but only get a few values to choose from (you picked 192.168.0. ), and then pick a random number for the machine (you picked 99). You can have multiple networks, e.g. 192.168.1. , but can't really combine two existing sets of networks together as they will likely clash. Using the private range 10.X.Y. gives you more options, but is still limited.
With IPv6, start with 'fd', followed by ten hex digits for your unique allocation (x), and four hex digits for your network (y). Each machine then have a number up to 16 hex digits (z).
This will give you a value like 'fdxx:xxxx:xxxx:yyyy:zzzz:zzzz:zzzz:zzzz', although if you put a lot of zeros in it will be a lot shorter to write out.
e.g. Pick '12:3456:789a' as your first random ten (x), and then use network '0001' inside that (y), then for your machine pick '0000:0000:0000:0063' (because hex 63 is the same as decimal 99).
This would give your machine the IPv6 address 'fd12:3456:789a:0001:0000:0000:0000:0063'. (For your specific network use different, random, values for the 12:3456:789a part.)
As you can collapse zeros in shorthand notation, this becomes just 'fd12:3456:789a:1::63'.
Your entire allocation would be 'fd12:3456:789a::/48', and subnet you are using would be 'fd12:3456:789a:1::/64'.
Note that the above examples happen to have the same number (99 decimal, 0x0063 hex) for the machine in both the IPv4 and IPv6 ranges, but they don't have to match (it just might be easier).
Firstly, there is no use in using a IPv6 address on a home network but still if you want to you then you should set it to automatic (just for IPv6), also your router must support DHCPv6 or Windows server will convert IPv4 to IPv6 automatically. As you want to try out into for static IPv6 Address then...
There are multiple types of IPv6 addresses that can be used, frankly speaking, even I don't know about them all. Below is a conversion table for the IPv4 specified. This is one of the best tool I can trust.
As far as I can say, you should use 2002:C0A8:63:0:0:0:0:0 as your static IPv6 Address. (I was using another format earlier but someone commented that the format should never be used on wire. I have myself switched to this format now.)
There is a similar ServerFault Question , I think this would help you a bit.
- 2 Addresses link 0:0:0:0:0:ffff:c0a8:0063 are so that software can use the IPv6 APIs even when communicating over IPv4. They must never be used on the wire (and therefor also not as an interface address)! – Sander Steffann Jan 6, 2013 at 14:22
- Okay, I have changed the IPv6 to 2002:C0A8:63:0:0:0:0:0 , its the 6-to-4 format – Akshat Mittal Jan 7, 2013 at 10:47
Yes if you are using NAT you don't have to move to IPv6 but 1) NAT is problematic, especially for Voice over IP services 2) NAT does not allow for incoming connections without setuo for each incoming connection and even then you are limited 3) NAT adds complication and increases routing time/effort
To answer the actual question asked you can encode an IPv4 address into an IPv6 address in the form ::FFFF:
So the IPv4 address of 22.214.171.124 can be represented in IPv6 as 0:0:0:0:0:FFFF:126.96.36.199 which is abreviated to ::FFFF:188.8.131.52
each section of the IPv4 address will be sent in Hex of course so a network trace will show ::FFFF:C0E1:9815 as 192=C0 in hex, 225=E1,152=98 in hex etc
This will be converted to the IPv4 address when leaving an IPv6 network and entering an IPv4 network
See this page has some info on this
There is no real need and probably no point to setting an IPv6 address on your internal network. Just stick with the IPv4 address and ignore the warning. The warning would be relevant for use on a public server so unless you have good reason for running IPv6 on your internal network I wouldn't worry about it.
On your other point, there is no IPv6 'translation' of an IPv4 address. They are separate systems.
In order to assign an IPv6 on your desktop, you would need to configure your internal router to manage an IPv6 network.
If you did want to run a home IPv6 network, then there are some helpful comments in the following questions:
- Is there any benefit to using IPv6 on my home network?
- How will home networks work in the IPv6 world?
- 8 I'd still like to, for correctness, even if it is optional. – myermian Jan 5, 2013 at 13:19
- You would need to also configure your router for IPv6 if you wanted to run an IPv6 network internally. There are some useful comments here: superuser.com/questions/43853/… – harunahi Jan 5, 2013 at 13:29
- 1 IPv6 is used in a lot more places than you think. Every interface has a link-local IPv6 address by default these days. Setting a global IPv6 address is usually only useful when your ISP provides it to you, but you can run a local IPv6 network using ULA (Unique Local Addresses). – Sander Steffann Jan 6, 2013 at 14:20
- 7 This was a mediocre answer in 2013; today it's dangerously out of date. – Michael Hampton Mar 11, 2017 at 23:21
Sign up or log in, post as a guest.
Required, but never shown
Not the answer you're looking for? Browse other questions tagged networking ipv6 static-ip ipv4 windows-server-2012 or ask your own question .
- The Overflow Blog
- Five Stack Exchange sites turned ten years old this quarter!
- “Move fast and break things” doesn’t apply to other people’s savings (Ep. 544)
- Featured on Meta
- We've added a "Necessary cookies only" option to the cookie consent popup
Hot Network Questions
- Gas furnace takes like 2-5 minutes from ignition to blower start. flame also burning yellow/orange
- Gimp not opening images in root folder
- Applying Geometry Generator for MultiPoint feature in QGIS
- God's presence among us
- Mando's Mandatory Meandering?
- Aligning polynomial expansion
- Is this a viable theoretical method of fast interplanetary space travel?
- Choice of GraphLayout to draw undirected graph
- Why do I get two different answers while doing this simple limit math?
- Does every US state set its standard deduction to match the federal one? Why?
- Pathfinder 2e help with a kobold draconic instinct barbarian build
- Is it inappropriate to tell my boss that "baby talk" is unprofessional?
- 〜のがほしい instead of 〜たい
- Pixel 5 vibrates once when turned face down
- How feasible are my Gauss weapons?
- Box character doesn't display properly in linux terminal
- Variance Among Coordinates of Multivariate Normal
- Running a computational calculation from Python
- Does oven polenta actually work?
- Compensation for train journey rerouting due to track-work (Sweden–Germany)?
- In a large list, should the filter and search be combined or separated?
- Create number 985 using 1 3 5 7 9
- Imtiaz Germain Primes
- What laws would Jesus be breaking if he were to turn water into wine today?
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
Guidance for configuring IPv6 in Windows for advanced users
- 5 minutes to read
- 7 contributors
Windows Vista, Windows Server 2008, and later versions of Windows implement RFC 3484 and use a prefix table to determine which address to use when multiple addresses are available for a Domain Name System (DNS) name.
By default, Windows favors IPv6 global unicast addresses over IPv4 addresses.
Original KB number: 929852
It is common for IT administrators to disable IPv6 to troubleshoot networking-related issues such as name resolution issues.
Internet Protocol version 6 (IPv6) is a mandatory part of Windows Vista and Windows Server 2008 and newer versions. We do not recommend that you disable IPv6 or its components. If you do, some Windows components may not function.
We recommend using Prefer IPv4 over IPv6 in prefix policies instead of disabling IPV6.
Use registry key to configure IPv6
Follow the steps in this section carefully. Serious problems might occur if you modify the registry incorrectly. Before you modify it, back up the registry for restoration in case problems occur.
The IPv6 functionality can be configured by modifying the following registry key:
Location : HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip6\Parameters\ Name : DisabledComponents Type : REG_DWORD Min Value : 0x00 (default value) Max Value : 0xFF (IPv6 disabled)
- Administrators must create an .admx file to expose the registry settings of below table in a Group Policy setting.
- You must restart your computer for these changes to take effect.
- Values other than 0 or 32 causes the Routing and Remote Access service to fail after this change takes effect.
By default, the 6to4 tunneling protocol is enabled in Windows when an interface is assigned a public IPv4 address (Public IPv4 address means any IPv4 address that isn't in the ranges 10.0.0.0/8, 172.16.0.0/12, or 192.168.0.0/16). 6to4 automatically assigns an IPv6 address to the 6to4 tunneling interface for each address, and 6to4 dynamically registers these IPv6 addresses on the assigned DNS server. If this behavior isn't desired, we recommend disabling the IPv6 tunnel interfaces on the affected hosts.
You can also follow these steps to modify the registry key:
Open an administrative Command Prompt window.
Run the following command:
Replace the <value> with the corresponding value.
How to calculate the registry value
Windows use bitmasks to check the DisabledComponents values and determine whether a component should be disabled.
To learn which component each bit (from low to high) controls, refer to the following table.
For each bit, 0 means false and 1 means true. Refer to the following table for an example.
Using the network properties GUI to disable IPv6 is not supported
This registry value doesn't affect the state of the following check box. Even if the registry key is set to disable IPv6, the check box in the Networking tab for each interface can be selected. This is an expected behavior.
For more information about RFC 3484, see Default Address Selection for Internet Protocol version 6 (IPv6) .
For more information about how to set IPv4 precedence over IPv6, see Using SIO_ADDRESS_LIST_SORT .
For information about RFC 4291, see IP Version 6 Addressing Architecture .
For more information about the related issues, see the articles below:
- Example 1: On Domain Controllers, you might run into where LDAP over UDP 389 will stop working. See How to use Portqry to troubleshoot Active Directory connectivity issues
- Example 2: Exchange Server 2010, you might run into problems where Exchange will stop working. See Arguments against disabling IPv6 and Disabling IPv6 And Exchange – Going All The Way .
- Example 3: Failover Clusters See What is a Microsoft Failover Cluster Virtual Adapter anyway? and Failover Clustering and IPv6 in Windows Server 2012 R2 .
Tools to help with network trace: Microsoft Network Monitor 3.4 (archive)
Netmon 3.4 isn't compatible with Windows Server 2012 or newer OS when LBFO NIC teaming is enabled. Use Message Analyzer instead.
Was this page helpful?
Configuring an Interface for IPv6 Static Mode
Static mode provides user a way to assign static IPv6 address as opposed to an auto-assigned address. Using static mode, the IPv6 interface can still listen for Router Advertisements and learn an autonomous address from the appropriate prefix option. Static Mode does not disturb the running of Stateless Address Autoconfiguration on IPv6 interface unless the user manually disables it.
The following diagram shows a sample topology with IPv6 configured in static mode.
Sample IPv6 Static Mode Configuration
Three types of IPv6 address are possible to assign under this mode:
To configure an interface for a static IPv6 address:
- Configuring IPv6 Addresses
- Configuring IPv6 Static Neighbors
Configuring IPv6 Default Gateway and Static IPv6 Routes
- Configuring Prefix Delegation
- Managing IP Addresses
- Configuring Multicast Listener Discovery
- Debugging IPv6
- Provisioning an IPv6 AP
The following procedure describes how to configure IPv6 default gateway Gateway is a network node that allows traffic to flow in and out of the network. .
- In the Managed Network node hierarchy, navigate to the Configuration > Interfaces > IP Routes tab.
- Click + under the Static Default Gateway accordion.
- Select IPv6 from the IP version drop-down list, and enter the IPv6 address in the IP address field.
- Click Submit to add the address to the IPv6 default gateway Gateway is a network node that allows traffic to flow in and out of the network. table.
- Click Pending Changes .
- In the Pending Changes window, select the check box and click Deploy changes .
The following procedure describes how to configure static IPv6 routes.
- Expand the IP Routes accordion.
- Click + under the IP Routes table.
- Select IPv6 from the IP version drop-down list.
- Enter the Destination IP address and the Forwarding settings .
- Click Submit to add the static route to the IPv6 routes table.
The following CLI Command-Line Interface. A console interface with a command line shell that allows users to execute text input as commands and convert these commands to appropriate functions. command configures the IPv6 default gateway Gateway is a network node that allows traffic to flow in and out of the network. .
(host) [md] (config)#ipv6 default-gateway <ipv6-address> <cost>
The following CLI Command-Line Interface. A console interface with a command line shell that allows users to execute text input as commands and convert these commands to appropriate functions. command configures static IPv6 routes.
(host) [md] (config)#ipv6 route <ipv6-prefix/prefix-length> <ipv6-next-hop> <cost>
<ipv6-next-hop> = X:X:X:X::X
- Write for Us!
- Cloud Computing
- all Topics...
Lead Image © James Steidl, 123RF.com
Configuring IPv6 in Windows with NetShell
Ipv6 on board.
The Windows input template for the network interface is fine for a basic IPv6 configuration ( Figure 1 ). You can define values such as the IPv6 address(es), prefix (typically "/64"), default gateway(s), and DNS server. However, IPv6 offers several other features that are not controllable via the standard configuration dialog. Also, the overview you get when you press Details is very rudimentary ( Figure 2 ). If you want to delve deeper into your IPv6 configuration, the tool you'll need is NetShell.
Working with NetShell
NetShell lets you customize and view almost all network-specific parameters for Windows and the TCP/IP stack. You can configure both IPv4 and IPv6 parameters. Although IPv4 often requires no further tuning, NetShell can be very useful for customizing IPv6 settings.
Launch NetShell by typing the netsh command at the command prompt. You can either type a complete command or use NetShell in interactive mode. If you have to enter multiple commands, interactive mode will save you some typing, and an interactive session also gives you access to NetShell's detailed help resources.
Be sure to launch the command prompt in administrative mode if you want to make changes to the configuration.
Entering netsh without any parameters starts interactive mode. The context for the IPv6 configuration is interface ipv6 ; you need to enter this in the terminal after launching the interactive shell. NetShell then displays the prompt netsh interface ipv6 .
You only need to type the command until the syntax becomes unambiguous. For example, instead of interface ipv6 , you can just type int ipv6 . Additionally, you can always access the contextual help by typing a question mark. The help system is simple, intuitive, and very useful. Exit quits the interactive NetShell.
IPv6 and MAC Addresses
NetShell uses show commands to display all configuration and status details for IPv6 and its subcomponents. For example, you can query the contents of the neighbor cache, which corresponds to the ARP cache in IPv4. (ARP was replaced in IPv6 by Neighbor Discovery.) When an IPv6 address is resolved into a link-layer address (MAC address), a corresponding entry is produced in the neighbor cache. Display the contents of this cache using the command:
If you are already in the right context, simply type show neighbor , or the short form sh n ( Figure 3 ).
For each interface, the IPv6-address to link-layer-address mappings are listed separately. Tunnel and pseudo-interfaces are given their own sections. In addition to unicast addresses, various multicast addresses are also listed.
In the line with Neighbor Unreachability Detection (NUD), each unicast record has a status, known as a "type"; possible values include:
- Reachable: The entry is valid; the MAC address can be used.
- Incomplete: The entry is invalid; the current MAC address could not be determined.
- Stale: The entry has exceeded a timeout value (the default is 30 seconds) and must be refreshed before its next use.
Static entries can map specific IPv6 addresses to the matching link layer addresses. To map an address, specify the interface, the IPv6 address, and the link-layer address, as follows:
If NetShell simply says "OK," or nothing at all, the command was accepted. An entry you define in this way appears in the Neighbor Cache as a "permanent" type.
Such configuration changes, however, basically only survive until the next reboot. If you want to save the changes permanently, add the configuration command using the store=persistent option. This option then applies to all configuration commands in NetShell.
Interfaces and Addresses
The ipconfig /all command provides a good general overview of the most important IP(v6) parameters, but it only scratches the surface. To obtain a comprehensive list of settings, you need NetShell. If you want an overview of your IPv6-enabled interfaces, use the command:
See Figure 4 . This command also displays the index number and the correct name of the interface. If the index of the interface is Local Area Connection 11, the command described above for a static neighbor cache entry would read as follows:
A comprehensive overview of the interface addresses is provided by the following command:
See Figure 5 . In addition to displaying the address type, this command also shows the validity and status. This information is particularly relevant in the context of autoconfiguration and it goes far beyond ipconfig /all 's ability to provide meaningful information.
Of course, you can again tweak various interface and address parameters. If you want to permanently add the IPv6 address 2001:db8:face::1 to your LAN connection interface with an index of 11, the command is as follows:
If this address is an anycast address, add anycast to the command.
An existing address is removed in a similar way. If you want to delete the address, try the command:
Caution: Do not enter a prefix, or NetShell will simply output an error message telling you that it needs a valid IPv6 address.
1 2 3 4 Next »
Buy this article as PDF
Buy admin magazine.
US / Canada
UK / Australia
Windows Firewall with Advanced Security was introduced in Vista/Windows Server 2008. Compared with the old Windows Firewall, it offers many new features and possibilities.
IPv6 is establishing itself in everyday IT life, and all modern operating systems from Windows, through Mac OS X, to Linux have it on board; but if you let IPv6 introduce itself into your environment, you could be in for some unpleasant surprises.
Traditional administration command-line tools such as ifconfig, route, and arp are almost as old as TCP/IP itself. We provide an overview of how the IPRoute2 toolkit now unifies the management of kernel network components.
Subscribe to our ADMIN Newsletters Find SysAdmin Jobs Subscribe to our Linux Newsletters Find Linux and Open Source Jobs
- %%title%% %%typeName%% %%icon%%
Adding an ipv4 or ipv6 address to windows server.
In this article, we explain how to 1) add a static IPv4 or IPv6 address and 2) how to add more than one IPv4 or IPv6 address to your Windows VPS. Click here for a manual on adding an IPv4 or IPv6 address to a Linux VPS.
Only static configurations allow for more than one IP address to be added. Steps 1 - 7 in the guides below show you how to staticly configure IP addresses. Step 8 and further shows how to add an additional IP address on top of that.
- This manual is about public IP addresses. In this manual , you will find more information about setting up internal addresses (for your private network).
- A VPS includes 1 IPv4 address by default, but you can expand this for X1-X8 VPSs to a maximum of 10 IPv4 addresses via the control panel. All PerformanceVPSs and X16 VPSs and larger have a maximum limit of 20 IPv4 addresses.
- In case a misconfiguration makes your VPS unreachable, it is best to create a snapshot first.
This article covers the following topics:
Adding an extra IPv4 or IPv6 address to your VPS:
- Ordering an extra IPv4 address in the control panel .
- Creating an extra IPv6 address in the control panel .
Configuring the extra IPv4 or IPv6 address on your VPS:
Windows Server 2008:
Windows Server 2012:
Windows Server 2016:
Ordering an IPv4 address in the control panel
A VPS includes 1 IPv4 address by default, but you can expand this to a maximum of 10 IPv4 addresses via the control panel. A maximum limit of 20 IPv4 addresses applies to the VPSs of the PRO series.
Log in to your control panel, navigate to the ' BladeVPS ' tab and click the name of your VPS on the left.
In the top right, click on ' Manage ', followed by ' Network information '.
Your shown an overview of your IP addresses. Click ' Request IPv4 addressess ' to order additional IP addresses.
Adding an IPv6 address in the control panel
Each VPS has a /64 IPv6 range at its disposal by default, where IP addresses can be added as desired. A /64 IPv6 range contains a total of 18,446,744,073,709,551,616 IP addresses, so the likeliness that you will not have enough is quite small!
Enter the desired IPv6 address and click ' Add IPv6 address '. Will you use this IP address to send e-mails from your VPS? Then also set your reverse DNS before adding the IPv6 address.
Windows Server 2008
Connect with the VPS using the VPS console or RDP and log in.
Once logged in, click start to go to the Control Panel.
Then click 'View network status and tasks' under 'Network and Internet' .
Next click 'Change adapter settings' .
Then right click on 'Local Area Connection' and then click on 'Properties' in the pop-up window.
In the overview that appears click 'Internet Protocol Version 4' and then click 'Properties' at the bottom right.
By default, DHCP is used, unless you have already modified it manually. DHCP only works for the first IPv4 address however.
If it is not yet the case, set the option to 'Use the following IP address' and fill in the details of your IP address which you can find in the control panel under ' Manage ' > ' Network Information '.
You'll need to manually configure the resolvers, which might already be done if, for example, you're using Google's resolvers (184.108.40.206). The TransIP resolvers can also be found in the control panel with the rest of the network information. At this point you can already check ' Validate settings upon exit '. With this option selected, Windows Server will test your configuration when you save the settings.
Are you only configuring a single static IP-address? Click ' Ok ' twice to finish your configuration. Are you configuring additional IP addresses? Click ' Advanced ' and proceed to the next step.
In the ‘ Advanced TCP/IP Settings’ screen click 'Add ...' to add a new IP. Be sure to set the subnet mask to 255.255.255.0 to prevent that you cannot reach IPs in the same network.
Click 'Add' to add the IP.
The extra IP address is now listed in the overview of IP addresses. If you want to add more IPs, repeat the above step.
Now click Ok to save the changes.
Click 'Ok' on the 'Internet Protocol Version 4 Properties' again and do not forget to turn on the ‘ Validate settings upon exit’ option.
Testing the IP address is more difficult because ping (icmp) is disabled by default in the Windows Firewall. Optionally you can find how to enable this on this website .
If you have enabled this, you can test this IP address by running a ping from another computer / IP, but you can also test this via our website , for example.
In the overview that appears click 'Internet Protocol Version 6' and then click on 'Properties' at the bottom right.
By default, the first IPv6 address should have been added here, unless you have removed it manually.
In the 'Advanced TCP / IP Settings' screen click 'Add ...' to add a new IP.
Add the extra IPv6 address here. Make sure you set subnet prefix length to 48 to prevent that you cannot reach IPs in the same network.
Now click ‘ Ok’ to save the changes.
Now click 'Ok' again on the 'Internet Protocol Version 6 Properties' screen and do not forget to turn on the ‘ Validate settings upon exit ’ option.
Windows will now test the configuration and the IP is added to the network interfaces.
Windows Server 2012
Connect with the VPS using the VPS console or RDP and log in.
Once logged in, click start to go to the Control Panel .
Then click on 'View network status and tasks' under 'Network and Internet' .
Next click on 'Change adapter settings' .
Then right click 'Ethernet' and click 'Properties' in the pop-up window.
I n the ‘ Advanced TCP/IP Settings’ screen click 'Add ...' to add a new IP. Make sure you put the subnet mask on 255.255.255.0 to prevent that you cannot reach IPs in the same network.
Now click ‘ Ok’ to save the changes.
If you have enabled this, you can test this IP address by running a ping test from another computer / IP.
In the overview that appears click 'Internet Protocol Version 6' and click 'Properties' in the bottom right.
In the 'Advanced TCP / IP Settings' screen click 'Add ...' to add a new IP.
Now click ' Ok ' to save the changes.
Windows Server 2016
Click on start, followed by the settings icon to go to the control panel.
Click ' Network & Internet '.
Next, click on 'Change adapter options' .
I n the ' Advanced TCP/IP Settings ' screen click 'Add ...' to add a new IP. Make sure you put the subnet mask on 255.255.255.0 to prevent that you cannot reach IPs in the same network.
Click 'Ok' in the 'Internet Protocol Version 4 Properties' screen again and do not forget to turn on the ‘ Validate settings upon exit’ option.
Windows Server 2019
By default, DHCP is used, unless you have already modified it manually.
Should you have any questions left regarding this article, do not hesitate to contact our support department. You can reach them via the ‘ Contact Us ’ button at the bottom of this page.
If you want to discuss this article with other users, please leave a message under ' Comments '.
Has this article been helpful?
Share this article.
- Share on Twitter
- Share on Facebook
- Share on LinkedIn
Create an account or log in to be able to leave a comment.
- Legal & Security
- TransIP API
- Prices exclude VAT
- BladeVPS PureSSD
- Big Storage
- Multiple Snapshots
- Operating Systems
- Domain registration
- New Web Hosting
- Knowledge Base
This tutorial explains how to configure a static IPv6 address in Windows 10.
In Settings go to Network & Internet and click the Properties button for the interface you wish to configure. Click the Edit button under IP
How to configure IPv6 in Windows · Log on to the server with administrator rights. · Go to Start > Network > Network and Sharing Center > Change Adapter Setting.
Firstly, there is no use in using a IPv6 address on a home network but still if you want to you
Configuring IPv6 with Manual Addresses · Click Start, point to Programs, point to Accessories, and then click Command Prompt. · At the command
Use registry key to configure IPv6 · Open an administrative Command Prompt window. · Run the following command: Console Copy. reg add "
Select Advertise Subnet Prefix of IPv6 Primary Static Address to add a default prefix into the interface advertising prefix list. This prefix is the subnet
Expand the IP Routes accordion. · Click + under the IP Routes table. · Select IPv6 from the IP version drop-down list. · Enter the Destination IP address and the
The Windows input template for the network interface is fine for a basic IPv6 configuration (Figure 1). You can define values such as the IPv6 address(es)
In the 'Advanced TCP / IP Settings' screen click 'Add ...' to add a new IP. ... Add the extra IPv6 address here. Make sure you set subnet prefix length to 48 to