Linked Questions
27 questions linked to/from How do I fix DNS resolving which doesn't work after upgrading to Ubuntu 13.10 (Saucy)
23
votes
4
answers
225k
views
"ping: unknown host google.com" but IPs works fine [duplicate]
I recently upgraded from Ubuntu 12.04 to Ubuntu 14.04. After restarting I have WiFi connected and/or LAN connection with no internet access. I'm using Toshiba Satellite C855D.
$ sudo lshw -C network
...
1
vote
1
answer
9k
views
Cannot ping by host name [duplicate]
I have a strange situation. Pinging by ip works fine, but by host name fails.
My observations:
nslookup -type=ns google.com
;; connection timed out; no servers could be reached
In one window I ...
8
votes
6
answers
15k
views
DNS problems after upgrading from 16.04 to 17.10: How to reset the DNS settings to default?
After upgrading from Ubuntu 16.04 to 17.10, the DNS settings doesn't seem to work anymore. I guess that this might have to do something with the migration from resolvconf to systemd-resolv.
How can I ...
10
votes
3
answers
10k
views
systemd-resolve does not forward DNS requests to stated DNS server
Anyone know how systemd-resolve voodo works?
192.168.1.30is the correct DNS server for my network, as returned by DHCP.
/etc/resolv.conf points to 127.0.0.53
Systemd claims to be using the correct ...
1
vote
2
answers
19k
views
DNS resolution not working in DHCP
I noticed this strange behaviour, I have a wi-fi network that only works with static IP addresses. If I set DHCP the DNS resolution fails, I can for example ping 8.8.8.8 but I can't surf the web or ...
6
votes
1
answer
4k
views
14.04 Resolving Host (DNS) Problem [closed]
UPDATE: Problem solved with 16.04.
I have an Asus Zenbook UX32V. I installed Ubuntu 14.04 and now I cannot browse the Internet. When I connect to a wireless network everything is fine for 2-3 ...
1
vote
0
answers
7k
views
Cannot access internet on Terminal, browser works fine
I am using Ubuntu 14.04 and connected to network through Ethernet. I am able to browse and connect to Internet via browser but having issue through terminal.
I tried to ping www.google.com from ...
0
votes
2
answers
2k
views
How do I configure DNS resolution if resolvconf doesn't work?
My /etc/resolv.conf will not be written so DNS resolution is not working.
I'm running Ubuntu Server 16.04.1 LTS in a virtual machine on our office server.
This is my /etc/network/interfaces:
# This ...
1
vote
1
answer
4k
views
Can't boot Ubuntu 18.04 -- missing 'lowerdir' -- failed to connect to lvmetad
I seem to have the same problem as Robin, and I have indeed had an nvidia driver installed. The last things I did were "apt get update" and "apt get upgrade". I'm able to login to recovery mode (as ...
0
votes
2
answers
4k
views
Ubuntu 14.04 failing apt update - connection failed security/archive.ubuntu.com
I am trying to run apt update on Ubuntu 14.04 installed from trusty-server-cloudimg-amd64.ova.
I can see the apt-get traffic is being allowed in the firewall.
I ran sudo apt update and below is what ...
1
vote
2
answers
3k
views
Auto edit resolv.conf on system startup
settings in resolv.conf are being overwritten every time I reboot my system.
How can I make it to be overwritten by scrip automatically after reboot in a way I want it?
0
votes
1
answer
3k
views
DHCP client no longer assigning DNS
Today for some reason my Ethernet adaptor stopped assigning DNS server info via DHCP request. Wifi works without problems.
I was getting this error in Chrome DNS_PROBE_FINISHED_BAD_CONFIG. I looked ...
2
votes
1
answer
2k
views
Screwed up DNS settings in 13.10
When I run
nslookup internal.foo.com
I get
Server: 127.0.1.1
Address: 127.0.1.1#53
** server can't find internal.foo.com: NXDOMAIN
For some reason, I am not getting the 172.17.51.3 ...
0
votes
1
answer
2k
views
Can't connect to internet Lubuntu 18.04
I can't connect to the internet with my Lubuntu 18.04. It shows the wifi adapter with the signal bars and says that it's connected, but Firefox says: can't connect to server and Sudo apt-get update ...
1
vote
0
answers
2k
views
How to repair DNS resolution in Ubuntu 16.04
Recently, name resolution failed on Ubuntu 16.04, and I worked around the problem by adding "nameserver 127.0.0.1" to /etc/resolv.conf (which fixed the problem)
I know I should not be manually ...