You are not logged in.
Sorry, this is written in machine translation.
Today I updated my Arch Linux for the first time in 3 months. After that I rebooted and it was no longer resolving DNS.
I was using NetworkManager and resolving DNS using dnsmasq.
Actually, I could have solved this problem by rewriting /etc/resolv.conf directly or using systemd-resolved, but I use network hotspots and would like to be able to resolve DNS using dnsmasq somehow.
At this time, restarting NetworkManager will generate an empty resolv.conf. The same problem probably occurs at startup.
I need your help.
Last edited by 04tm34l (2022-04-10 13:51:31)
Offline
Retrace the steps outlined in the Wiki.
Make sure dnsmasq is still installed, unconfigured, systemd-deactivated and can be run by NetworkManager.
Offline
When I retraced the fix, there was a change in /etc/resolv.conf. However, it is not a fundamental solution, and after restarting NetworkManager or the system, /etc/resolv.conf is empty again and DNS resolution is no longer possible.
Offline
O.K. - can you verify via
sudo ss -l -u -n -p
that dnsmasq is running and listening on 127.0.0.1:53?
Last edited by -thc (2022-04-10 13:29:49)
Offline
I am sorry.
I ran the command and dnsmasq was working correctly.
The problem was that my network provider seems to make it impossible to use any DNS. I solved the problem by making sure I use the DNS resolver provided by my provider.
Thanks.
Offline