DNS request timed out in command prompt

Anonymous
2023-01-25T04:59:30+00:00

Hello, I've been experiencing issues with Halo MCC giving me this weird microstutter when I play online. In diagnosing it I've reinstalled windows completely, tried multiple sets of hardware (3 motherboards, 2 processors, 2 sets of ram, 2 graphics cards, 2 power supplies, and two SSDs). The only thing that's stayed the same is the actual license for Windows as it has booted fine on all 3 mobo's. Additionally, I had the problem on Win11, downgraded back to 10, then eventually upgraded back to 11 and the problem has persisted each time. I also did full clean repair installs everytime I swapped out the motherboard or SSD and installed my chipset drivers from a USB drive I saved them to.

With that out of the way, the mobo currently in my machine is an ASRock B450mac with a Realtek LAN card, just for reference. (The 2 other boards have Intel LAN cards).

I have Verizon gigabit fiber internet and I'm hardwired to a G3100 router. I have tried factory reseting the router and multiple cables. Additionally, the in-game network problems happen irrespective of my server ping. It happens on <20ms ping just as bad as 150ms.

I'm not sure if this is related, but when I run "nslookup <website name here>" in command prompt, it always says DNS request timed out after 2 seconds. However, if I turn on a VPN, it seems to work. Additionally, I've tried changing my DNS provider in both Windows and my router's settings and the problem persists. I tried flushing my DNS cache in command prompt last night which fixed it, but today the nslookup command says DNS request timed out again, regardless if I reset the cache.

I also have DNS-related events in event viewer as well as one from the Browser service.

I'm wondering why command prompt is saying this, and how to fix it.

Thank you.

Windows for home | Windows 11 | Internet and connectivity

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments

46 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2023-01-26T05:35:11+00:00

    Okay, booted into Win on a local account but sfc still found corruptions and nslookup isnt working still

    Was this answer helpful?

    0 comments
  2. Anonymous
    2023-01-26T05:34:07+00:00

    Great, since the forums software removed the (email?) fix you said worked, can you explain it for others who will want to know?

    Was this answer helpful?

    0 comments
  3. Anonymous
    2023-01-26T05:29:28+00:00

    I can connect to the internet during setup fine, but the workarounds to force a local connection call for you to disconnect the connection. I'm just saying that when I try them they no longer work. Instead of giving me the option to make a local account it just tells me to reconnect again.

    Actually,the ******@test.com solution worked for me. I'm setting up a local account now.

    Was this answer helpful?

    0 comments
  4. Anonymous
    2023-01-26T05:16:12+00:00

    Then you ran Clean All instead of Clean which is instant. It isn't necessary to zero every sector to clean the Boot Sector and partition table which is what's required.

    Are you getting these errors plugged into ethernet? Have you tried other cables, updating LAN driver, trying Wifi, or a USB wifi adapter?

    Was this answer helpful?

    0 comments
  5. Anonymous
    2023-01-26T04:59:25+00:00

    It says that it will take about an hour or less to clean the drive, it's running now.

    I just tried the workarounds and those are all patched on my end. What happens when I lose connection is it says "You've lost connection. Let's go back and connect to your network again." With the only button on the screen being "Retry".

    Was this answer helpful?

    0 comments