Question

7

Hostnames cannot be resolved after upgrading to 22.04

rated 0 times [ 7] [ 0] / answers: 1 / hits: 25368 / 3 Years ago, sun, june 6, 2021, 12:17:09

After upgrading ubuntu from 21.10 to 22.04, my internet connection does not work anymore. I am connected to the WLAN and I can ping IP addresses (from the local network as well as from the internet) - however, resolving names does not work anymore. So ping 151.101.65.69 works with 0% packet loss but ping askubuntu.com gives me an error Name or service not known (it works from another machine that is connected to the same router).

When running nmcli, it shows the following DNS configuration:

DNS configuration:

    servers: 192.168.17.1

    domains: fritz.box

    interface: wlp64s0

I also tried manually adding 8.8.8.8 to the DNS servers in the network manager (WiFi setting -> IPv4 -> DNS). Then, both servers are shown in the DNS configuration but the problem still persists.

Any idea what the reason could be, what I can do to narrow down the problem or how to solve it?

Answers

Only authorized users can answer the question. Please sign in first, or register a free account.

anatta

Add To Favorites

Follow

Total Points: 326

Total Questions: 128

Total Answers: 96

Location: Jordan

Member since Sun, Jun 26, 2022

2 Years ago

anatta questions

1 Wlan0 will not connect to WiFi?

Sun, Jul 17, 22, 07:13, 2 Years ago

1 Using Steam's Proton to run Roblox

Sat, Jun 12, 21, 20:43, 3 Years ago

1 Add "My App" to Context Menu in Ubuntu

Thu, Jan 13, 22, 20:49, 2 Years ago

1 phpMyAdmin is not working in ubuntu 20.04 with php5.6

Sat, Jun 5, 21, 05:39, 3 Years ago

1 Troubles with libpng12.so.0 - no version information available?

Tue, Jan 25, 22, 06:51, 2 Years ago

View All

answered 3 Years ago llael · Accepted Answer

As pointed out in this answer and in this answer, the solution (at least in my case) was a problem with /etc/resolv.conf which only contained a commented out line "Generated by NetworkManager". Replacing that file with a symlink to /run/resolvconf/resolv.conf solved the problem for me:

sudo rm -f /etc/resolv.conf

sudo ln -s /run/resolvconf/resolv.conf /etc/resolv.conf