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
DNS not working in fresh Ubuntu 18.04 that installed from Windows Store #3268
Comments
Have you tried using the |
@3antrt67 |
In that case, have you tried the |
@3antrt67
|
I have done a fresh install from the Windows Store of Ubuntu 18.04 and the above issue cannot be replicated. The ping itself works with no issue as per the
The output you have provided shows that the command can read from the Have you run through |
Just mentioning #469 here, because for some people there antivirus / firewall settings did interfere. It also may be worthwhile to post the complete (failing) output of just And, perhaps, try updating your version of Windows to the latest Windows 10 release, in case that is possible? |
@3antrt67 No I haven't run |
I would certainly recommend running through at least Also just to clarify, can you run |
@3antrt67 DNS is not working for |
@VMatrix1900 Is it possible to provide the full output of the Thanks for the clarification on Windows side! With some perseverance on the output side I am sure we can find out some more.. |
@3antrt67
|
Indeed the Could you try the answer as provided in this question - https://askubuntu.com/questions/91543/apt-get-update-fails-to-fetch-files-temporary-failure-resolving-error |
@3antrt67 I tried the answer. Not working. I think the problem is the same with |
I am hard pressed to believe that it is DNS as handled by 18.04, since that would mean Have you tried the earlier kernel distro for Ubuntu that is on the store? From my side both iterations function without issue regarding DNS. |
@3antrt67 Ubuntu 16.04 works fine. But not 18.04. |
@VMatrix1900 There are a few other methods of DNS resolution to ascertain further possible errors. Can you try Also can you try the |
Dig works fine. But sudo ping baidu.com does not work.
发件人: 3antrt67
发送时间: 2018年6月19日 23:32
收件人: Microsoft/WSL
抄送: Vincent Stone; Mention
主题: Re: [Microsoft/WSL] DNS not working in fresh Ubuntu 18.04 thatinstalled from Windows Store (#3268)
@VMatrix1900 There are a few other methods of DNS resolution to ascertain further possible errors.
Can you try dig baidu.com for example?
Also can you try the ping baidu.com from the root user? I.E. sudo - root followed by the ping once logged in as root.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.
|
Having the same issue.I can used
|
@BlackFrog1 Could you please provide the output of |
I am an end user not proficient in DNS but Ido suspect I have the same problem reported in this thread, which apparently has been outstanding several weeks. So I think I'll admin my new system some different way than WSL until this is resolved. In the meantime here is some information so others may judge whether I indeed have the same problem and maybe to help diagnose what's going on. If it would help for me to run some commands to collect more information just let me know. I installed WSL June 21 and was able to install several applications using apt. However, on June 23 when I attempted to install another package I got the message “Temporary failure accessing archive.ubuntu.com.” Experimentation showed that I can't ping any hostname under WSL, only IP addresses. So, .I can't successfully ping google.com but can ping its IP, 172.217.11.38. Hostname pings still work fine in regular PowerShell, just not under bash. I suspect the change was caused by the installation of Windows 10 Home Edition Version 1803 on June 22. My WSL configuration is Linux LAPTOP-3HE8OLDR 4.4.0-17134-Microsoft |
Hi @onewnan, would it be possible to open a command prompt (using Would it be possible within the 18.04 shell to try @VMatrix1900 Are you still unable to update your Windows version? |
@3antrt67 Yes. My Windows update is controlled by my school. I do not know when they will push the 1803 version. |
@benhillis FYI since it hasn't received any notice for almost a month. Not sure if this is an 18.04 specific bug so your insight would help with this issue. |
*ver*
Microsoft Windows [Version 10.0.17134.112]
withing the bash shell
me@LAPTOP-3HE8OLDR:/mnt/c/Users/onewn$* dig google.com <http://google.com>*
; <<>> DiG 9.10.3-P4-Ubuntu <<>> google.com
;; global options: +cmd
;; connection timed out; no servers could be reached
|
@onewnan You are on the same Windows version as myself testing here. Within your There is a previous bug with 18.04 #1731522 that required AAAA records to convert from UDP to TCP transmission due to packet size and this change being denied by systemd. Although in that instance, |
*cat /etc/resolv.conf*
# This file was automatically generated by WSL. To stop automatic
generation of this file, remove this line.
nameserver 192.168.1.1
ping 192.168.1.1
*PING 192.168.1.1 (192.168.1.1) 56(84) bytes of data.*
^C
--- 192.168.1.1 ping statistics ---
73 packets transmitted, 0 received, 100% packet loss, time 73567ms
That's interesting, so I need to manually configure? How?
…On Thu, Jun 28, 2018 at 7:07 AM 3antrt67 ***@***.***> wrote:
@onewnan <https://github.com/onewnan> You are on the same Windows version
as myself testing here. Within your /etc/resolv.conf file, is it IPv4 set
addresses, IPv6 or both? If it is possible to show the output of ```cat
/etc/resolv.conf```` that could also help.
There is a previous bug with 18.04 #1731522
<https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1731522> that
required AAAA records to convert from UDP to TCP transmission due to packet
size and this change being denied by systemd.
Although in that instance, dig should still function if only querying A
records...
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#3268 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AmsouuHznQffCWEsrk_SFEh0KLlmaiIlks5uBNUhgaJpZM4UWUwF>
.
|
@onewnan Using the |
*me@LAPTOP-3HE8OLDR:/mnt/c/Users/onewn/Backups$ ifconfig*
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Global
UP LOOPBACK RUNNING MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
wifi0 Link encap:UNSPEC HWaddr
9C-B6-D0-ED-4C-8D-00-00-00-00-00-00-00-00-00-00
inet addr:192.168.1.33 Bcast:192.168.1.255 Mask:255.255.255.0
inet6 addr: fe80::40a9:40da:413f:3a2c/64 Scope:Global
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
*PS C:\Users\onewn> ipconfig | findstr /i "Gateway"*
Default Gateway . . . . . . . . . : 192.168.1.1
…On Thu, Jun 28, 2018 at 10:39 AM 3antrt67 ***@***.***> wrote:
@onewnan <https://github.com/onewnan> Using the ifconfig command, what is
the output for your interface? Also on the Windows OS side, can you tell me
what the Gateway for your internet connection is? Is it 192.168.1.1 as
resolv.conf has been informed?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#3268 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/Amsout7x0lrvgqjtibVTUEAcCoYFXlWZks5uBQbcgaJpZM4UWUwF>
.
|
@onewnan So your system is using WiFi connection and not Ethernet? To confirm visible connection on the ip |
Yes, wifi. Ping works both from Powershell and bash:
PS C:\Users\onewn> ping 192.168.1.33
Pinging 192.168.1.33 with 32 bytes of data:
Reply from 192.168.1.33: bytes=32 time=4ms TTL=128
Reply from 192.168.1.33: bytes=32 time=5ms TTL=128
Reply from 192.168.1.33: bytes=32 time=7ms TTL=128
Ping statistics for 192.168.1.33:
Packets: Sent = 3, Received = 3, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 4ms, Maximum = 7ms, Average = 5ms
Control-C
PS C:\Users\onewn> bash
me@LAPTOP-3HE8OLDR:/mnt/c/Users/onewn$ ping 192.168.1.33
PING 192.168.1.33 (192.168.1.33) 56(84) bytes of data.
64 bytes from 192.168.1.33: icmp_seq=1 ttl=128 time=5.53 ms
64 bytes from 192.168.1.33: icmp_seq=2 ttl=128 time=11.3 ms
64 bytes from 192.168.1.33: icmp_seq=3 ttl=128 time=5.39 ms
64 bytes from 192.168.1.33: icmp_seq=4 ttl=128 time=11.0 ms
^C
--- 192.168.1.33 ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3003ms
rtt min/avg/max/mdev = 5.394/8.309/11.308/2.848 ms
me@LAPTOP-3HE8OLDR:/mnt/c/Users/onewn$
|
I've run into the same problem. Occurs when having a Wireguard tunnel open at the same time, even if that tunnel is only for non-internet traffic. In my case, I had a wg tunnel to 192.168.10.0/24 for dev servers. Deactivating the tunnel immediately resolves the issue. Activating the tunnel immediately breaks WSL again. |
This worked for me |
This one worked for me. (WSL1) There wasn't anything in |
I have resolved my issue by deleting Checkpoint VPN Client. Now it works correctly. |
I am experiencing the same issue, and I have tried every suggestion. ipconfig output:
wsl2 ifconfig output:
/etc/resolv.conf has this IP: (I also tried 8.8.8.8) Default gateway is empty for Ethernet adapter vEthernet (WSL). Is that the problem or is it because the ip address in eth0 (172.20.116.125) is different from the WSL ethernet ip address (172.20.112.1)? |
What's the output for DNS Servers when you type "ipconfig /all" in powershell? Does it show the correct values? |
I don't understanding networking very well, so diffiuclt for me to say if all of this is correct. I see that DHCP is disabled on the wsl adapter, I'm not sure if it should be enabled. Here's the output of
|
Well, thoses aren't the right addresses for DNS Servers. I can only suggest you what worked for me. |
@rellbits I have checked my router config and it already has my ISP DNS servers set for primary and secondary. That's the default and can't be changed. I tried to turn off I'm not sure how the WSL DNS Servers get those addresses, but I'll look into more about that. Thank you for pointing me in the right direction. EDIT Now in Powershell
|
today, I meet the same problem, all domain in wsl will resolve to 192.168.0.52 ,This is not correct. I don't konw what's wrong.
|
The issue seems to correlate with truncation of UDP DNS responses, at least in my case - all DNS responses that are reported by nslookup as trucated are triggering the same "Temporary" resolution issue in ping (and node) |
This issue is still ongoing. Fresh install of WSL Ubuntu 18.04 on Windows 10 Pro (v1709 build 16299.1625) done last week (15th of January). Same symptoms, can nslookup any domain, but pinging them is not working. Simply replacing the resolv.conf to use public DNS servers is not changing the outcome. Curiously enough, on another PC with the same Windows version (it's a corporate image), WSL Ubuntu 18.04 was installed longer ago last year and maintained up to date every week (apt-get update; apt-get upgrade; apt-get clean), and doesn't have the problem. This leads me to believe that something broke along the way. It would be interesting to try installing an older WSL package to see if that changes something, but I can only download the latest version (is there an archive somewhere?) I also confirm that the problem doesn't exist with WSL Ubuntu 16.04. I just did a fresh install and DNS resolution was fine. |
I don't believe your issue is related to this one. The symptoms are totally different. |
Kali Linux, Ubunutu 18.04, and also Ubuntu 16.04 are all facing this problem so are completely unusable. for me unfortunately. I have tried several fixes with no luck, I hope that they can improve these apps. No ping to websites, temporary failure resolving on apt-get update. No antivirus. vpn, or firewall. |
just installed ubuntu 18.04 LTS after other versions were uninstalled. can't ping things. super weird. windows 10 build 17763 |
I also have this issue. Windows 10 1909 v18363.657, fresh install of Ubuntu from Windows Store, name resolution broken. Edited resolv.conf manually works around the issue, after |
i view this page for hours,until i see your posts i know it's becase of VPN。and then i find the solution。 it works! |
Sometimes, maybe the windows vpn clint like easyclinet will effect the dns conf in wsl. |
This just happened to me. All changes pointed out here broke my setup - my fix was to remove anything custom I had done with nameserver, auto generate, etc and simply ensure my terminal was running as admin... I had the exact same symptoms described here so it's possible there's going to be at least one other person with this issue. |
Faced same issue was not able to resolve github or ubuntu repos lets say from WSL - in my case it was corrupted |
Same here! My PC blue screened then when I restarted it What is the default value inside Update: I added Update 2: Found a permanent fix below: #3268 (comment) |
Same here. /etc/resolv.conf is ^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@ |
To restore
Then close all bash windows and open a fresh one. Open up |
Faced a similar issue - was not able to resolve GitHub from WSL. My computer was connected to VPN. After disconnecting from the VPN, i was able to resolve the hosts. Seems strange but do not understand why that happened. |
Hi folks, we have put out a new update that aims to address networking issues in WSL. In your More info on this release and the changes can be found here in the blog post. Please note: You need to be on a Windows Insiders version to use the new networking settings (Any channel of Windows Insiders will do, including release preview). If you see the "These are not supported" messages it means that your current Windows version doesn't have support, and you will need to upgrade. These features will eventually be coming to Windows 11 22H2. Please use the megathread for more DNS discussion: #8365 |
@craigloewen-msft are these changes also coming to Windows 10 22H2? |
Your Windows build number: 10.0.16299.431
What you're doing and what's happening:
Ubuntu 18.04 installed from Windows Store can not resolve domain names.
ping xxx.xxx.xxx.xxx
works fine, butping baidu.com
does not work.ifconfig
returns following result:sudo systemctl status resolvconf
returns:The content of
/etc/resolv.conf
is:192.168.1.1 is my router's ip address.
At the same time, everything works fine in Ubuntu 16.04 installed from Windows Store works fine.
The text was updated successfully, but these errors were encountered: