Manjaro 5.15 LTS running. I have no trouble to ping a website by IPs. But when I try to ping a website by DNS name, I get: > “Temporary failure in name resolution”
Few attempts at “troubleshooting”:
The problem comes accross different networks (home/office) and different modalities (ethernet/WiFi).
I believe the system runs NetworkManager.service and the IPv4 Settings’ method is “Automatic (DHCP)”
I tried at some point to overwrite the “resolv.conf”, as suggested on some websites, or to force the DNS server via the advanced network interface, but it did not appear to have done much, so I reverted.
Thanks in advance.
NB.: I do not recall having installed anything lately that could have triggered the issue.
Probably DNS server which you use is down. Try other DNS provider (you can set it in network settings), two most popular are:
Google: 8.8.8.8, 8.8.4.4
Cloudflare: 1.1.1.1, 1.0.0.1
but you can try any other server.
To do what @Tomek said, you have to change that method in NetworkManager settings to:
Automatic (DHCP) Addresses only
then you can set your own nameserver like 1.1.1.1 for example
Or you do the similar thing in your router configuration, so it will use a working nameserver
and you will not have to change it on every device connected through it.
Thank you, it seems the issue is not (only) about the DNS servers I am using, for three main reasons – but I may be wrong.
when I use the Network Interface to shift from “DHCP (Automatic)” to “DHCP (Automatic) addresses only” and add ‘8.8.8.8’ to DNS, it does not change much (even after restarting the service)
when I overwrite the resolv.conf generated by NetworkManager with ‘8.8.8.8’, it does not change much;
the NetworkManager, if I understand correctly, receives the DNS from my ISP provider, other computers in the house do just fine;
in the configuration you had
DHCP (Automatic)
it receives the DNS server from the router - which in turn gets its DNS from your ISP
with:
DHCP (Automatic) addresses only
you can choose your own nameserver over the one provided by the ISP
but
if other devices, which connect through the same router, are working just fine
the issue is not likely to be the DNS server that your router (your ISP) provides
I’m not experienced with NetworkManager so I don’t know how to fix it.
Apparently, it configures your loopback device over IPv6 as DNS which doesn’t seem sensible.
Don’t know. Neever set it up manually. When looking online, it looks like it might be related to protonVPN. I am happy to get rid of the Interface / VPN, if necessary.
You are trying to fix something - then you got dns problems as a result - and now you are trying to fix the dns error without solving the underlying issue.
So you are asking for help to fix a dns issue without telling us you have been fidling with vpn?
That would be nice - at least so it is possible to know it is not interfering.
There is nothing wrong with a pristine Manjaro system with relation to dns or networking and unless there is upstream regressions - which happens occasionally - with NetworkManager - updates doesn’t cause dns issues.
This is becoming more and more difficult to help with - because we cannot possibly know which changes you have made before consulting the forum so we are practically blind with relation to how to suggest you solve the issue.
I solved the problem : (1) I got rid of ProtonVPN (via Pamac), (2) I deleted the interface (sudo nmcli connection delete pvpn-ipv6leak-protection), (3) I reverted to Automatic DNS (undoing what I had done, following Networking - Manjaro), (4) I restarted the computer.
@linux-aarhus:
Thanks for your help – I did no change before consulting the forum, I believe I mostly wrongly assumed that ProtonVPN did not mess with DNS / Interfaces. For next time, do you have suggestions for sending the content of a console in text format from a computer that has no internet connection?