Hello,
I have closed the bug as Jakeforster suggestion on the issue tracker
fixed the problem :
Deleting /etc/resolv.conf followed by
`sudo herd restart NetworkManager` solves the problem. After this, the
/etc/resolv.conf is automatically recreated with the correct
nameservers entries AND the file is also automatically updated after a
manual change to a nameserver through the Gnome UI for the network
interface.
Thanks for your inputs.
On 6/20/26 20:21, Jack Hill wrote:
I belielve I ran into this too, but didn't realize it was an update v.
something I did. My symptom was that /etc/resolv.conf had the contents
from a previously connected network that I hadn't connected to in over
a year. I eventually just removed /etc/resolv.conf and restarted
NetworkManager and things worked again, so maybe try that workaround?
Best,
Jack
