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

Temporary failure in name resolution after installing VirtualBox 6.1.34 #8457

Closed
1 of 2 tasks
YevheniiPokhvalii opened this issue May 28, 2022 · 3 comments
Closed
1 of 2 tasks

Comments

@YevheniiPokhvalii
Copy link

YevheniiPokhvalii commented May 28, 2022

Version

0.58.3.0

WSL Version

  • WSL 2
  • WSL 1

Kernel Version

5.10.102.1

Distro Version

Ubuntu 22.04

Other Software

VirtualBox 6.1.34

> wsl --status
Default Distribution: Ubuntu
Default Version: 2
WSL version: 0.58.3.0
Kernel version: 5.10.102.1
WSLg version: 1.0.33
MSRDC version: 1.2.2924
Direct3D version: 1.601.0
Windows version: 10.0.22000.675

Repro Steps

  1. Install VirtualBox 6.1.34
  2. Reboot the system
  3. Enter WSL
  4. ping google.com

Also, I am able to ping 8.8.8.8, I can ping my router gateway from WSL, but I can't ping the automatically assigned nameservers by WSL:

$ cat /etc/resolv.conf | grep -B 1 nameserver
# generateResolvConf = false
nameserver 172.17.192.1
$ ping 172.17.192.1
PING 172.17.192.1 (172.17.192.1) 56(84) bytes of data.

I tried solutions with firewalls but it did not help: #4171 (comment)
The solution with sudo bash -c 'echo "nameserver 8.8.8.8" > /etc/resolv.conf' works but it does not work when I enable VPN which I do quite often.

The issue happened just right after I installed VirtualBox. Uninstalling VirtualBox did not help.
Also, I tried to re-enable Hyper-V - still not result.
Network flush did not help either: #3438 (comment)

Expected Behavior

I am able to ping google.com

Actual Behavior

$ ping google.com
ping: google.com: Temporary failure in name resolution

Diagnostic Logs

On windows:

> netsh interface ip show config "vEthernet (WSL)"

Configuration for interface "vEthernet (WSL)"
    DHCP enabled:                         No
    IP Address:                           172.17.192.1
    Subnet Prefix:                        172.17.192.0/20 (mask 255.255.240.0)
    InterfaceMetric:                      5000
    Statically Configured DNS Servers:    None
    Register with which suffix:           None
    Statically Configured WINS Servers:   None
> netsh interface ip show config "vEthernet (VirtualBox Host)"

Configuration for interface "vEthernet (VirtualBox Host)"
    DHCP enabled:                         No
    IP Address:                           172.24.176.1
    Subnet Prefix:                        172.24.176.0/20 (mask 255.255.240.0)
    InterfaceMetric:                      5000
    Statically Configured DNS Servers:    None
    Register with which suffix:           None
    Statically Configured WINS Servers:   None

On Ubuntu WSL:

$ ip a l eth0
6: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1400 qdisc mq state UP group default qlen 1000
    link/ether 00:15:5d:76:eb:9f brd ff:ff:ff:ff:ff:ff
    inet 172.17.194.220/20 brd 172.17.207.255 scope global eth0
       valid_lft forever preferred_lft forever
    inet6 fe80::215:5dff:fe76:eb9f/64 scope link
       valid_lft forever preferred_lft forever
@YevheniiPokhvalii
Copy link
Author

YevheniiPokhvalii commented May 28, 2022

It seems to be working with VPN when I add my WIFI router gateway IP as a nameserver to WSL:

> netsh interface ip show config "WiFi"

Configuration for interface "WiFi"
    DHCP enabled:                         Yes
    IP Address:                           192.168.0.106
    Subnet Prefix:                        192.168.0.0/24 (mask 255.255.255.0)
    Default Gateway:                      192.168.0.1
    Gateway Metric:                       0
    InterfaceMetric:                      50
    DNS servers configured through DHCP:  192.168.0.1
    Register with which suffix:           Primary only
    WINS servers configured through DHCP: None
sudo bash -c 'echo "nameserver 192.168.0.1" > /etc/resolv.conf'

What caused this issue?

@OneBlue
Copy link
Collaborator

OneBlue commented May 31, 2022

/dupe #8365

@ghost
Copy link

ghost commented May 31, 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 31, 2022
@ghost ghost added the duplicate label May 31, 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

2 participants