Windows 10: A race condition issue while ping, IPv6 AAAA DNS, Error message: could not find host.

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.















***Modified Title from: ping -4 sends out an IPv6 AAAA DNS request causing a could not find host race condition error***

:)

 

Unable to ping local host and network issues

Evening everyone,

I'm having issues trying to connect my computer to the internet. Originally the issue was that the Ethernet cable doesn't have a valid IP configuration. I then proceed to use Command Prompt to run <netsh winsock reset> and <netsh int ip reset>. The second command
wasn't working correctly so I had to go into the registry to allow the command to work. Here's a general list of things I've done.

• Diabled and enabled the adapter
• Swapped ethernet cables
• Tried different ports on router
• Check to see if DHCP was enabled
• Updated adapter drivers
• Disabled all anti-virus and firewalls in safe mode to see if I can ping localhost

Here's where it gets interesting, I can't ping the local host. It gives me a "General Failure" comment. Now, I've gone ahead and set up a static IP address for my computer using Google's DNS server (8.8.8.8) but I still can't access the internet and regardless
of what I do I can't ping the local host.

Window's diagnostic for my ethernet adapter is that it works but the DNS isn't working.

Any and all help would be appreciated.

 

IPV6 Ping Not Working?

We are glad that you are now able to ping IPv6 addresses. Since your device issue is different from what is previously posted, we suggest that you post a new thread so other community members would be able to assist you.

Should you have further queries, feel free to post it.

 

DNS errors - nslookup works but ping doesn't after Windows 10 upgrade

I have various dns issues in my browsers. In testing, I have discovered that nslookup ALWAYS works but ping doesn't.

There are older Google results that suggest disabling ipv6 - but there does not appear to be ipv4 in Windows 10

ipconfig /flushdns cleared the problem but then it came back and I don't want to be jumping into the command prompt every 5 minutes

Any thoughts?

Thanks, Vincent