windows server 2012 is not resolving IPv6 address from local host file

[jimab2611]

Hi Experts ,

Windows server 2012r2 server is not resolving IPV6 address from local host file . There is no DNS entry for IPV6 and hence I added IPV6 address for my tool server in C:\windows\system32\drivers\etc\host file . But server failed to resolve the name . Server is still able to resolve IPV4 from host file without any issue. problem is only with IPV6. Both IPV4 and IPV6 enabled in NIC settings . Could you please advise if any solution for this

thanks . Jim

 

[Neemobeer]

Is there some requirement for IPv6? Most systems will favor using an IPv4 address since IPv6 still isn't heavily adopted.

 

[jimab2611]

Hi Neemobeer,

yes. couple of tool servers are using IPV6 and there is no DNS record for IPV6 . Hence for name resolution, we have added localhost file entries for these tool servers. I just noticed that issue is not only with 2012 servers, but also for few 2016 .

 

[Neemobeer]

Do you have IPv6 enabled?

 

[jimab2611]

Do you have IPv6 enabled?

Yes. IPV6 enabled on NIC properties . Compared with another working server , but could not find any difference .

 

[Rex M]

Windows Server 2012 R2 may not be resolving IPv6 addresses from the local host file for a number of reasons. You might attempt the following troubleshooting steps:

Verify the IPv6 address: Make that the IPv6 address you entered in the host file is accurate and corresponds to the server's actual IPv6 address. The "ipconfig" command in the command prompt can be used to determine the server's IPv6 address.

Verify the host file: Make sure the host file is constructed correctly and that the IPv6 address entry is free of typos and syntax problems. An IPv6 address should be formatted as follows in the host file:

IPv6_address hostname

Restart the DNS Client service: Try restarting the server's DNS Client service. You can do this by accessing the Control Panel's Services applet, looking for the "DNS Client" service, and selecting the "Restart" button.

Disable IPv6 Teredo interface: Try turning off the IPv6 Teredo interface on the server to see if it fixes the problem. You can accomplish this by typing "netsh interface Teredo set state disabled" at an elevated command line.

Check for firewall rules: Inspect the server or network to see if any firewall rules are preventing IPv6 traffic. Make sure that any firewalls are configured to permit communication using the required ports and protocols for IPv6.

You might need to speak with a network administrator or get in touch with Microsoft Support for more help if the problem still exists after following these steps.