Pinging own machine returns an IPv6 address instead of IPv4

Question

When I ping my own machine I get an IPv6 address:

Reply from fe80::1004:p8f0:9e40:a42c%10: time<1ms
Reply from fe80::1004:p8f0:9e40:a42c%10: time<1ms

I used to get the IPv4 address (eg. 192.168.1.5) from the router.

Why has it changed?

@djerry: just a Win7 Pro machine connected wirelessly to the router. — CJ7, May 2, 2012 at 11:52
@CraigJ: djerry is asked what you are pinging. The address you get is determined by the name resolution method. If it is localhost, then it is likely to return IPv6 every time. — Nick Whaley, May 5, 2012 at 19:13

Community · Accepted Answer · 2017-04-13 12:14:40Z

8

This could be due to caching or the DNS. On a Windows Server 2008 issue on Server Fault they suggest:

If they are resolving to IPv6 they might be cached or have ipv6 addresses registered in DNS.

You can also add a -4 to the ping:

ping example.com -4

CommunityBot

1

answered May 2, 2012 at 11:45

Terry

1,6593 gold badges19 silver badges24 bronze badges

When I use the -4 I get the IPv4 address. Any reason it is defaulting to IPv6 instead of IPv4?
– CJ7
May 2, 2012 at 11:55
1

@CraigJ: On Windows, IPv6 is always preferred over IPv4.
– Nick Whaley
May 5, 2012 at 19:14

Add a comment |

CJ7 · Accepted Answer · 2012-05-02 12:24:38Z

0

My problem was solved by running ipconfig /flushdns from the command prompt.

answered May 2, 2012 at 12:10

CJ7

1,13915 gold badges45 silver badges59 bronze badges

@ekaj: or link to the serverfault question, as the answer on there is what helps the OP.
– Terry
May 2, 2012 at 12:34

Add a comment |

2 Answers 2