{"id":553,"date":"2025-12-16T03:44:08","date_gmt":"2025-12-16T03:44:08","guid":{"rendered":"https:\/\/faq.powervps.ru\/?p=553"},"modified":"2026-10-01T11:40:11","modified_gmt":"2026-10-01T11:40:11","slug":"%d0%bd%d0%b0%d1%81%d1%82%d1%80%d0%be%d0%b9%d0%ba%d0%b0-%d0%bf%d1%83%d0%b1%d0%bb%d0%b8%d1%87%d0%bd%d0%be%d0%b9-ipv6-%d0%bf%d0%be%d0%b4%d1%81%d0%b5%d1%82%d0%b8-hetzner-%d0%b2-windows-server-2019","status":"publish","type":"post","link":"https:\/\/faq.powervps.xyz\/?p=553","title":{"rendered":"How to Configure a Public Hetzner IPv6 Subnet on Windows Server 2019"},"content":{"rendered":"<h1 style=\"text-align: center;\">How to Configure a Public Hetzner IPv6 Subnet on Windows Server 2019<\/h1>\n<p>If your Hetzner server has been assigned a public IPv6 subnet, such as a <code>\/64<\/code>, you can configure multiple IPv6 addresses on your Windows Server.<\/p>\n<p>This can be useful for services and applications that need to use specific IPv6 addresses for outbound connections.<\/p>\n<p>This guide explains how to configure a Hetzner IPv6 subnet on <strong>Windows Server 2019<\/strong> using both the graphical interface and PowerShell.<\/p>\n<p><strong>Important:<\/strong> Before changing network settings, make sure you have access to the server through the Hetzner KVM or another recovery console. Incorrect network settings may interrupt your RDP connection.<\/p>\n<h2>Example Network Configuration<\/h2>\n<p>In this guide, we will use the following example IPv6 subnet:<\/p>\n<ul>\n<li><strong>IPv6 subnet:<\/strong> <code>2a01:4f9:123:abcd::\/64<\/code><\/li>\n<li><strong>Server IPv6 address:<\/strong> <code>2a01:4f9:123:abcd::2<\/code><\/li>\n<li><strong>Prefix length:<\/strong> <code>64<\/code><\/li>\n<li><strong>IPv6 gateway:<\/strong> <code>fe80::1<\/code><\/li>\n<\/ul>\n<p><strong>Important:<\/strong> Replace the example IPv6 subnet and addresses with the values assigned to your server.<\/p>\n<p>For Hetzner dedicated servers and supported virtual server platforms, the IPv6 gateway is normally:<\/p>\n<p><code>fe80::1<\/code><\/p>\n<p>You can verify the network information assigned to your server in the Hetzner control panel.<\/p>\n<h2>Step 1. Open the Network Adapter Settings<\/h2>\n<p>Open:<\/p>\n<p><code>Control Panel \u2192 Network and Internet \u2192 Network and Sharing Center \u2192 Change adapter settings<\/code><\/p>\n<p>Locate the network adapter connected to the Internet. It is usually named <strong>Ethernet<\/strong>.<\/p>\n<p>Right-click it and select <strong>Properties<\/strong>.<\/p>\n<h2>Step 2. Open the IPv6 Settings<\/h2>\n<p>In the adapter properties, select:<\/p>\n<p><strong>Internet Protocol Version 6 (TCP\/IPv6)<\/strong><\/p>\n<p>Click <strong>Properties<\/strong>.<\/p>\n<h2>Step 3. Configure the Primary IPv6 Address<\/h2>\n<p>Select:<\/p>\n<p><strong>Use the following IPv6 address<\/strong><\/p>\n<p>Enter the following values:<\/p>\n<ul>\n<li><strong>IPv6 address:<\/strong> <code>2a01:4f9:123:abcd::2<\/code><\/li>\n<li><strong>Subnet prefix length:<\/strong> <code>64<\/code><\/li>\n<li><strong>Default gateway:<\/strong> <code>fe80::1<\/code><\/li>\n<\/ul>\n<p>You must use the IPv6 address assigned to your own server instead of the example address above.<\/p>\n<h2>Step 4. Configure IPv6 DNS Servers<\/h2>\n<p>You can use the DNS servers provided by Hetzner or another DNS provider.<\/p>\n<p>For example, Cloudflare DNS:<\/p>\n<pre><code>2606:4700:4700::1111\r\n2606:4700:4700::1001<\/code><\/pre>\n<p>Or Google Public DNS:<\/p>\n<pre><code>2001:4860:4860::8888\r\n2001:4860:4860::8844<\/code><\/pre>\n<p>Click <strong>OK<\/strong> to save the settings.<\/p>\n<p>Then close the remaining network configuration windows.<\/p>\n<h2>Step 5. Add Additional IPv6 Addresses<\/h2>\n<p>A <code>\/64<\/code> IPv6 subnet contains a very large address range.<\/p>\n<p>You can assign additional addresses from your subnet to the same Windows network adapter.<\/p>\n<p>For example:<\/p>\n<pre><code>2a01:4f9:123:abcd::10\r\n2a01:4f9:123:abcd::11\r\n2a01:4f9:123:abcd::12<\/code><\/pre>\n<p><strong>Important:<\/strong> Do not use addresses that are already assigned to another device or service.<\/p>\n<h3>Add Additional IPv6 Addresses via GUI<\/h3>\n<p>Open the IPv6 properties again and click <strong>Advanced&#8230;<\/strong>.<\/p>\n<p>Under <strong>IP addresses<\/strong>, click <strong>Add&#8230;<\/strong>.<\/p>\n<p>Enter the additional IPv6 address and use:<\/p>\n<p><strong>Subnet prefix length:<\/strong> <code>64<\/code><\/p>\n<p>Repeat this process for every additional IPv6 address you want to use.<\/p>\n<p>You do <strong>not<\/strong> need to configure a separate gateway for each additional IPv6 address.<\/p>\n<h2>Configure IPv6 Using PowerShell<\/h2>\n<p>PowerShell can be more convenient when configuring multiple addresses or automating server setup.<\/p>\n<p>Open <strong>PowerShell as Administrator<\/strong>.<\/p>\n<h3>Step 1. Find the Network Interface Name<\/h3>\n<p>Run:<\/p>\n<pre><code class=\"language-powershell\">Get-NetAdapter<\/code><\/pre>\n<p>Locate the network interface connected to the Internet.<\/p>\n<p>In this example, the interface is named:<\/p>\n<p><code>Ethernet<\/code><\/p>\n<h3>Step 2. Configure the Primary IPv6 Address<\/h3>\n<p>Run:<\/p>\n<pre><code class=\"language-powershell\">New-NetIPAddress `\r\n    -InterfaceAlias \"Ethernet\" `\r\n    -IPAddress \"2a01:4f9:123:abcd::2\" `\r\n    -PrefixLength 64 `\r\n    -DefaultGateway \"fe80::1\"<\/code><\/pre>\n<p>Replace <code>Ethernet<\/code> and the IPv6 address with the values used by your server.<\/p>\n<h3>Step 3. Add Additional IPv6 Addresses<\/h3>\n<p>For example:<\/p>\n<pre><code class=\"language-powershell\">New-NetIPAddress -InterfaceAlias \"Ethernet\" -IPAddress \"2a01:4f9:123:abcd::10\" -PrefixLength 64\r\n\r\nNew-NetIPAddress -InterfaceAlias \"Ethernet\" -IPAddress \"2a01:4f9:123:abcd::11\" -PrefixLength 64\r\n\r\nNew-NetIPAddress -InterfaceAlias \"Ethernet\" -IPAddress \"2a01:4f9:123:abcd::12\" -PrefixLength 64<\/code><\/pre>\n<p>No additional default gateway is required for these secondary addresses.<\/p>\n<h2>Disable Temporary IPv6 Addresses<\/h2>\n<p>Windows may automatically create temporary IPv6 addresses for outgoing connections.<\/p>\n<p>If you need applications to use the static IPv6 addresses you configured, you can disable temporary IPv6 addressing.<\/p>\n<p>Open <strong>PowerShell as Administrator<\/strong> and run:<\/p>\n<pre><code class=\"language-powershell\">Set-NetIPv6Protocol -RandomizeIdentifiers Disabled\r\nSet-NetIPv6Protocol -UseTemporaryAddresses Disabled<\/code><\/pre>\n<p>You can then check the configured IPv6 addresses again.<\/p>\n<h2>Verify the IPv6 Configuration<\/h2>\n<h3>Check Assigned Addresses<\/h3>\n<p>Run:<\/p>\n<pre><code>ipconfig \/all<\/code><\/pre>\n<p>Verify that the expected IPv6 addresses appear on the correct network adapter.<\/p>\n<h3>Test IPv6 Connectivity<\/h3>\n<p>Run:<\/p>\n<pre><code>ping -6 google.com<\/code><\/pre>\n<p>If IPv6 connectivity is working, you should receive replies over IPv6.<\/p>\n<h3>Check the Public IPv6 Address<\/h3>\n<p>Run:<\/p>\n<pre><code>curl -6 https:\/\/ifconfig.co<\/code><\/pre>\n<p>The command should return the IPv6 address currently being used for the outbound connection.<\/p>\n<h2>Check the IPv6 Route<\/h2>\n<p>You can also verify the IPv6 routing table using:<\/p>\n<pre><code class=\"language-powershell\">Get-NetRoute -AddressFamily IPv6<\/code><\/pre>\n<p>Look for the default IPv6 route:<\/p>\n<p><code>::\/0<\/code><\/p>\n<p>The gateway should normally be:<\/p>\n<p><code>fe80::1<\/code><\/p>\n<h2>Using Multiple IPv6 Addresses<\/h2>\n<p>After multiple IPv6 addresses have been assigned to the network adapter, Windows and individual applications can use them for network connections.<\/p>\n<p>Common use cases include:<\/p>\n<ul>\n<li>Web services<\/li>\n<li>API connections<\/li>\n<li>Proxy services<\/li>\n<li>VPN and tunnel configurations<\/li>\n<li>Mail services<\/li>\n<li>Applications that support binding to a specific local IPv6 address<\/li>\n<\/ul>\n<p>Applications that support source-address binding can be configured to use a specific IPv6 address from the assigned subnet.<\/p>\n<h2>Troubleshooting<\/h2>\n<p>If IPv6 does not work after configuration, check the following:<\/p>\n<ul>\n<li>The IPv6 address belongs to the subnet assigned to your server.<\/li>\n<li>The prefix length is set to <strong>64<\/strong>.<\/li>\n<li>The default gateway is configured as <code>fe80::1<\/code>.<\/li>\n<li>The IPv6 address is not already in use.<\/li>\n<li>Windows Firewall is not blocking the required traffic.<\/li>\n<li>The correct network adapter was configured.<\/li>\n<\/ul>\n<p>You can display all IPv6 addresses configured on the server with:<\/p>\n<pre><code class=\"language-powershell\">Get-NetIPAddress -AddressFamily IPv6<\/code><\/pre>\n<p>You can display the routing table with:<\/p>\n<pre><code class=\"language-powershell\">Get-NetRoute -AddressFamily IPv6<\/code><\/pre>\n<h2>Conclusion<\/h2>\n<p>Your Windows Server 2019 is now configured to use the public IPv6 subnet assigned by Hetzner.<\/p>\n<p>You can add multiple static IPv6 addresses from the subnet to the same network interface and configure applications to use specific addresses when required.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>How to Configure a Public Hetzner IPv6 Subnet on Windows Server 2019 If your Hetzner server has been assigned a public IPv6 subnet, such as a \/64, you can configure multiple IPv6 addresses on your Windows Server. This can be useful for services and applications that need to use specific IPv6 addresses for outbound connections. [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1],"tags":[55],"class_list":["post-553","post","type-post","status-publish","format-standard","hentry","category-dedicated-servers","tag-how-to-configure-a-public-hetzner-ipv6-subnet-on-windows-server-2019"],"_links":{"self":[{"href":"https:\/\/faq.powervps.xyz\/index.php?rest_route=\/wp\/v2\/posts\/553","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/faq.powervps.xyz\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/faq.powervps.xyz\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/faq.powervps.xyz\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/faq.powervps.xyz\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=553"}],"version-history":[{"count":3,"href":"https:\/\/faq.powervps.xyz\/index.php?rest_route=\/wp\/v2\/posts\/553\/revisions"}],"predecessor-version":[{"id":740,"href":"https:\/\/faq.powervps.xyz\/index.php?rest_route=\/wp\/v2\/posts\/553\/revisions\/740"}],"wp:attachment":[{"href":"https:\/\/faq.powervps.xyz\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=553"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/faq.powervps.xyz\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=553"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/faq.powervps.xyz\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=553"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}