win10 localhost resolves to:: 1 solution

Problem:

In cmd, ping localhost resolves the IPV6:: 1 Because Windows has a prioritized parsing list, which occurs when the IPv6 priority is higher than IPv4. Online there is a way to modify the registry, by opening regedit, navigating to HKEY_LOCAL_MACHINE \ SYSTEM \ currentcontrolset \ Services \ tcpip6 \ Parameters, creating dis Abledcomponents the DWORD registry value, set its value to 20 (hexadecimal), and then restart the computer. I tried this method, but I couldn't solve it.

I used the method of modifying the priority to resolve, that is, to modify the record of IPv4 priority above IPv6 to the precedence parse table. Here's how:

1. Right-click Win10 home----> Command Prompt (Admin) (a) (just open cmd with admin privileges)

2. Input command netsh interface ipv6 show prefixpolicies, query IPv6 priority

Please note that the IPV6 address (::/0) takes precedence over the IPV4 address (::/,:: FFFF:0:0/96), so we can develop a strategy so that IPV6 is no more advantageous than any IPV4 address. Where the label represents the priority, 0 is the highest priority, and so on.

Now you need to set the order to::/96,:: FFFF:0:0/96 priority higher than::/0 and:: 1/128, set priority on the command line:

netsh int ipv6 set prefix::/96 50 0
netsh int ipv6 set prefix:: FFFF:0:0/96 40 1
netsh int ipv6 set prefix 2002::/16 35 2
netsh int ipv6 set prefix 2001::/32 30 3
netsh int ipv6 set prefix:: 1/128 10 4
netsh int ipv6 set prefix::/0 5 5
netsh int ipv6 set prefix FC00::/7 3 13
netsh int ipv6 set prefix FEC0::/10 1 11
netsh int ipv6 set prefix 3FFE::/16 1 12

After that, enter the command netsh interface ipv6 show prefixpolicies to view the priority level:

As you can see, at this time::/,:: FFFF:0:0/96 priority higher than::/0. Ping localhost,

Ok.

win10 localhost resolves to:: 1 solution