Resolv.conf

Mascaret

Hello! Just did the systemd update (eopkg up; sudo sync; log off then power off).
No errors upon reboot.
Alas, firefox fails to connect..
ping 1.1.1.1 does succeed.
/etc/resolv.conf now points to /run/systemd..resolv.conf which does not exist.
Suggestion?
Thanks for your interest!

Mascaret

Answering to myself : updated another solus install. Successfully this time.
Copied the resolv.conf from that gig to the faulty one (/var/run/NetworkManager).
DNS works now. I can answer to myself with the other machine.

Mascaret

Still working upon reboot, /etc/resolv.conf now pointing to /var/run/NetworkManager.
But now I default to only 1.1.1.1, not my provider's dns.
Does that ring a bell? Explanations welcomed here!!

kyrios

/etc/resolv.conf is a symbolic link to /var/run/NetworkManager/resolv.conf
This file is generated by network manager and should not be edited

If you want to change your DNS, right-click on the network applet -> Edit Connections -> Select the network connection you want to edit and click on the gear icon, then you'll find your way I guess..

Mascaret

Thks for your interest!
What surprised me was that /etc/resolv.conf pointed to /run/systemd/resolv.conf which didn't exist..?
The network applet however used my provider's dns. But name resolution failed (probably not available to other clients).
This untilI I corrected /etc/resolv.conf and let it see correct nameservers.
However, NetrworkManager doesn't seem to identify my provider's dns and reverts to 1.1.1.1 (which is not a problem).
I can't fathom what happened and would be pleased to undestand.
Anyway, case is solved..