Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

WSL2 - DNS Issues(Temporary failure in name resolution) with VMWare workstation pro installed #8390

Closed
1 of 2 tasks
zhizhang77 opened this issue May 9, 2022 · 3 comments
Closed
1 of 2 tasks

Comments

@zhizhang77
Copy link

Version

Microsoft Windows [version 10.0.19044.1645]

WSL Version

  • WSL 2
  • WSL 1

Kernel Version

Linux version 5.10.102.1-microsoft-standard-WSL2 (oe-user@oe-host) (x86_64-msft-linux-gcc (GCC) 9.3.0, GNU ld (GNU Binutils) 2.34.0.20200220) #1 SMP Wed Mar 2 00:30:59 UTC 2022

Distro Version

Ubuntu 20.04

Other Software

VMware® Workstation 16 Pro: version 16.2.3 build-19376536

Repro Steps

I've used WSL2 on this PC for one year on this PC and it works perfect for me until yesterday. I installed VMware® Workstation 16 Pro together with Virtual Machine Platform. After reboot sudo apt update get jammed.

An interesting detail is I can ping internet successfully before sudo apt update , but after that "Temporary failure in name resolution" appears when I'm pinging the same website. Try it a few minutes later and it works again.

Editing /etc/resolv.conf and set nameserver to 8.8.8.8 will resolve the issue temporary but I want to dig out the root cause if possible...

btw. I could't access my microsoft account in win10 after VMWare is installed. Disabling VMware network adapter fixed this issue . But it won't help the WSL2 problem.

Expected Behavior

sudo apt update work as usual.

Actual Behavior

130019

Diagnostic Logs

No response

@OneBlue
Copy link
Collaborator

OneBlue commented May 10, 2022

/dupe #8365

@ghost
Copy link

ghost commented May 10, 2022

Hi! We've identified this issue as a duplicate of another one that already exists in this repository. This specific instance is being closed in favor of tracking the concern over on the referenced thread.

Thanks for your report!

@ghost ghost closed this as completed May 10, 2022
@ghost ghost added the duplicate label May 10, 2022
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants
@OneBlue @zhizhang77 and others