windows host dns fails after a docker build in wsl2

[fchastanet]

Windows Version

Microsoft Windows [Version 10.0.22621.2861]

WSL Version

2.0.14.0

Are you using WSL 1 or WSL 2?

• WSL 2
• WSL 1

Kernel Version

5.15.133.1

Distro Version

Ubuntu 20.04

Other Software

Google Chrome 120.0.6099.130

Repro Steps

• build any docker image
• open a web page in any windows browser (chrome, firefox or edge), dns is not working anymore and i receive this message
  
• dns randomly works again after 1 to 10 minutes
• there is not dns issues on wsl2 only windows dns is impacted

Expected Behavior

dns resolution should work on windows host after a wsl docker build

Actual Behavior

dns resolution does not work on windows for 10 minutes host after a wsl docker build

Diagnostic Logs

I created this stackoverflow question, and I tried the suggested fixes without any success

I tried to search for similar issues, but I just found people having dns issues on wsl not on host.
Please tell me if I could provide any other kind of logs to identify the issue.

Following your guidelines I tried from windows cmd

tracert github.com

with the following result:

Tracing route to github.com [140.82.121.4]
over a maximum of 30 hops:

  1     1 ms     1 ms     1 ms  192.168.0.254
  2    18 ms    17 ms    18 ms  station11.multimania.isdnet.net [194.149.174.108]
  3     *       26 ms    26 ms  decix.proxad.net [80.81.192.223]
  4    30 ms    31 ms    49 ms  de-cix.fra.github.com [80.81.196.79]
  5     *        *        *     Request timed out.
  6     *        *        *     Request timed out.
  7    25 ms    25 ms    25 ms  lb-140-82-121-4-fra.github.com [140.82.121.4]

ping github.com

Pinging github.com [140.82.121.4] with 32 bytes of data:
Reply from 140.82.121.4: bytes=32 time=25ms TTL=250
Reply from 140.82.121.4: bytes=32 time=25ms TTL=250
Reply from 140.82.121.4: bytes=32 time=25ms TTL=250
Reply from 140.82.121.4: bytes=32 time=44ms TTL=250

Ping statistics for 140.82.121.4:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 25ms, Maximum = 44ms, Average = 29ms

logs sent by mail with the following subject "Issue #10994"

[github-actions]

Hi I'm an AI powered bot that finds similar issues based off the issue title.

Please view the issues below to see if they solve your problem, and if the issue describes your problem please consider closing this one and thumbs upping the other issue to help us prioritize it. Thank you!

Open similar issues:

• [WSL2] Cannot access windows service running on host from a container using host.docker.internal (#6364), similarity score: 0.82
• Can't connect to docker container running inside WSL2 (#4983), similarity score: 0.79
• WSL 2 does not resolve local hostnames as it does in Windows (DNS issue) (#5224), similarity score: 0.79

Closed similar issues:

• WSL2 Docker Service makes it unable to ping host machine (#4602), similarity score: 0.82
• Localhost connections from Windows to WSL2 have stopped working (presumed docker desktop related) (#5606), similarity score: 0.81

Note: You can give me feedback by thumbs upping or thumbs downing this comment.

[chanpreetdhanjal]

Hi. Can you please collect networking logs by following the instructions below?
https://github.com/microsoft/WSL/blob/master/CONTRIBUTING.md#collect-wsl-logs-for-networking-issues

[fchastanet]

Hello, I sent logs sent by mail to [email protected] with the following subject "Issue #10994"

[chanpreetdhanjal]

@craigloewen-msft can you share the logs?