Windows 10: ping -4 sends out an IPv6 AAAA DNS request causing a could not find host race condition error

Hi I'm finding that trying to ping even when using the -4 option is causing a problem because Windows simultaneously asks for both the IPv6 and IPv4 when trying to resolve a hostname with a local DNS. The parallel requests is causing a race condition where ping sometimes fails. When ping gets back the DNS "AAAA" it responds with "could not find host" failing immediately even though there is a valid "A" response for IPv4 in the following response. If the "A" record comes back before the "AAAA" record then the ping is successful otherwise I see a "could not find host". Thus the race condition. Is this going to be fixed? For now I solved this by turning off IPv6 on my router to prevent it responding to "AAAA" requests but this is not ideal.

:)

 

IPV6 Ping Not Working?

I am running Windows 10 and am having some connectivity problems with the Internet and my WiFi router. While investigating this, I saw some strange behavior while trying to ping external websites. The command prompt defaults to IPv6, and the pings appear
to be blocked. If I provide a -4 flag on the ping, it goes through.

C:\Users\User>ping google.com

Pinging google.com [2607:f8b0:4009:816::200e] with 32 bytes of data:

Request timed out.

Request timed out.

Request timed out.

Request timed out.

Ping statistics for 2607:f8b0:4009:816::200e:

Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

C:\Users\User>ping google.com -4

Pinging google.com [172.217.6.110] with 32 bytes of data:

Reply from 172.217.6.110: bytes=32 time=31ms TTL=56

Reply from 172.217.6.110: bytes=32 time=36ms TTL=56

Reply from 172.217.6.110: bytes=32 time=31ms TTL=56

Reply from 172.217.6.110: bytes=32 time=31ms TTL=56

Ping statistics for 172.217.6.110:

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

Minimum = 31ms, Maximum = 36ms, Average = 32ms

Any ideas how I can either default to the IPv4 ping or hopefully successfully ping a IPv6 address? When I test my IPv6 compatibility through the Google test site (Ready for the future of the Internet?), I get this response:

Ready for the future of the Internet?

No problems detected.

You don’t have IPv6, but you shouldn’t have problems on websites that add IPv6 support.

 

Safe DNS Project

AFAIK, which really aint much here, if you can block duplicate, before the "ANY", requests per [*insert* time frame] that may help reduce a few numbers without being too limiting. If you can trace the source of requests, I dont why you cant add specific IPs to your blacklisting, even if temporary.

 

Browser /connection security, hosts file and DNS service

You're saying that Open DNS(and other services like it) house their own list of known 'bad' sites, and by using their DNS servers, it will filter out sites based on that list?

Would you believe I was already using Open DNS servers.
This means the hosts file is moot?

And furthering that, if there's any bespoke sites I want to manually add, I could do it through my router directly.

Thus I can empty my local hosts file and turn my DNS service back on?