If you’re doing a lot of network tinkering, configuring LAN-based apps and server tools, or just curious, you’ve likely noticed that there’s a difference between the localhost the local IP address. Read on to learn the differences.
Today’s Question & Answer session comes to us courtesy of SuperUser—a subdivision of Stack Exchange, a community-driven grouping of Q&A web sites.
SuperUser reader Diogo wants to know why the ping command treats the localhost and the local IP address differently when, on the surface, they appear to be the same thing:
Using cmd and ping on Windows gave me the following results:
Pinging “192.168.0.10″ (local IP address):
Aren’t both situations exactly the same?
I mean, I’m pinging the same interface, the same machine and the same address. Why do I get such different results?
Obviously there is a difference of some sort, but what exactly is going on when you switch between the two?
SuperUser contributor Tom Wijsman offers the following insight into the subtle differences between the two:
You are not pinging the same interface, without any physical interfaces you still have a “local host”.
localhostis used to refer to your computer from its “internal” IP, not from any “external” IPs of your computer. So, the ping packets don’t pass through any physical network interface; only through a virtual loop back interface which directly sends the packets from port to port without any physical hops.
You might still wonder why
localhostis resolving to
::1, while traditionally we would expect it to resolve to the IPv4 address
127.0.0.1. Note that
.localhostis traditionally a TLD (see RFC 2606) which points back to the loop back IP address (for IPv4, see RFC 3330, especially 127.0.0.0/8).
... Name: localhost Addresses: ::1 127.0.0.1
Thus Windows prefers to use the IPv6 loop back IP address
::1(see RFC 2373) as it is listed first.
Okay, so, where does it come from, let’s look at the hosts file.
... # localhost name resolution is handled within DNS itself. # 127.0.0.1 localhost # ::1 localhost ...
Hmm, we have to look at the DNS settings of Windows.
This KB article tells us about a setting that affects what Windows prefers, emphasized in bold:
- In Registry Editor, locate and then click the following registry subkey:
- Double-click DisabledComponents to modify the DisabledComponents entry.Note: If the DisabledComponents entry is unavailable, you must create it. To do this, follow these steps:
- In the Edit menu, point to New, and then click DWORD (32-bit) Value.
- Type DisabledComponents, and then press ENTER.
- Double-click DisabledComponents.
- Type any one of the following values in the Value data: field to configure the IPv6 protocol to the desired state, and then click OK:
0to enable all IPv6 components. (Windows default setting)
0xffffffffto disable all IPv6 components, except the IPv6 loopback interface. This value also configures Windows to prefer using Internet Protocol version 4 (IPv4) over IPv6 by modifying entries in the prefix policy table. For more information, see Source and Destination Address Selection.
0x20to prefer IPv4 over IPv6 by modifying entries in the prefix policy table.
0x10to disable IPv6 on all nontunnel interfaces (on both LAN and Point-to-Point Protocol [PPP] interfaces).
0x01to disable IPv6 on all tunnel interfaces. These include Intra-Site Automatic Tunnel Addressing Protocol (ISATAP), 6to4, and Teredo.
0x11to disable all IPv6 interfaces except for the IPv6 loopback interface.
- Restart the computer for this setting to take effect.
What is this prefix policy table?
netsh interface ipv6 show prefixpolicies(or
prefixpolicyon earlier versions)
Precedence Label Prefix ---------- ----- -------------------------------- 50 0 ::1/128 45 13 fc00::/7 40 1 ::/0 10 4 ::ffff:0:0/96 7 14 2002::/16 5 5 2001::/32 1 11 fec0::/10 1 12 3ffe::/16 1 10 ::/96
This table decides what prefixes get precedence over other prefixes during DNS resolves.
Ah, so using that KB we could add entries here that denote that IPv4 has higher precedence than IPv6.
Note: There is no reason to override this behavior, unless you are experiencing compatibly problems. Changing this setting on our Windows Server broke our mail server, so it should be handled with care…
There’s nothing we like more than a thorough and informative answer with linked support documents to spare. Clearly the localhost and local IP address are distinct entities, serve different purposes, and now we all know why.
Have something to add to the explanation? Sound off in the the comments. Want to read more answers from other tech-savvy Stack Exchange users? Check out the full discussion thread here.
Jason Fitzpatrick is warranty-voiding DIYer and all around geek. When he's not documenting mods and hacks he's doing his best to make sure a generation of college students graduate knowing they should put their pants on one leg at a time and go on to greatness, just like Bruce Dickinson. You can follow him on Google+ if you'd like.
- Published 03/14/13