Greetings everyone, I'm trying to get ipv6 name resolution working using hosts file. It works ok for IPv4 addresses but I've tried many formats for and still can't get it to translate IPv6 hosts, see below my attempts:
Regards - Philippe asked 06 Jan '11, 00:52 moction edited 06 Jan '11, 09:19 SYN-bit ♦♦ |
One Answer:
According to the prefix fe80, these are all IPv6 link-local addresses. You should use the global or site-local addresses instead. In an IPv4 address, the subnet mask specifies which part of the address is the network ID. A multi-homed system will have a different network ID for each interface. IPv6 link-local addresses, on the other hand, all have the same prefix. Therefore, the address by itself, is not sufficient to determine which interface should be used for link-local traffic. See IPv6 address - Link-local addresses and zone indices which has a brief explanation of why the IPv6 address of an interface by itself is not sufficient for the local computer to make a routing decision and discusses the use of a zone ID to differentiate the interfaces. Also see TCP/IP Fundamentals for Microsoft Windows Chapter 7 - Host Name Resolution. Microsoft states "For IPv6 entries, the address in the Hosts file entry is a global or site-local IPv6 address expressed in colon hexadecimal notation." Then there is an example of a Hosts file with both IPv4 and IPv6 entries (but no link-local addresses). Followed by "You should not place entries for link-local addresses in the Hosts file because you cannot specify the zone ID for those addresses." answered 06 Jan '11, 20:13 Jim Aragon edited 06 Jan '11, 23:06 Jaap ♦ Jaragon, the original poster is trying to do reverse-lookup with wireshark. These will be the addresses he is seeing (which is what you will see on a network that doesn't have a IPv6 router configured - it will only have link-local addresses) (06 Jan '11, 22:48) martyvis |
Is this still a problem? Just tried that out and works perfectly fine with 1.6.2