-
Disable and stop the systemd-resolved service:
sudo systemctl disable systemd-resolved.service sudo systemctl stop systemd-resolved
-
Then put the following line in the
[main]
section of your/etc/NetworkManager/NetworkManager.conf
:dns=default
-
Delete the symlink
/etc/resolv.conf
rm /etc/resolv.conf
-
Restart network-manager
sudo service network-manager restart or sudo systemctl restart NetworkManager.service
-
-
Save zoilomora/f7d264cefbb589f3f1b1fc2cea2c844c to your computer and use it in GitHub Desktop.
Following these steps on a fresh Ubuntu 22.10 install completely breaks dns
Local dns servers are perfectly functional, Ubuntu sees them and they show in network config, but it refuses to use them, what gives?
How do you solve the DNS issue for 22.10 please?
root@www::> systemctl disable systemd-resolved:> systemctl stop systemd-resolved
root@www:
root@www::> rm -f /etc/resolv.conf:> cat < /etc/resolv.conf
root@www:
nameserver 9.9.9.9
nameserver 8.8.8.8
nameserver 1.1.1.1
EOF
root@www:~:> reboot
Why not just rename instead of remove?
mv /etc/resolv.conf /etc/resolv.conf.del
@euntae: With just stopping instead of also disabling systemd-resolved it will be active again after a reboot but the way you described it the entries in resolv.conf won't get used anyway at least on Ubuntu 24.
I was going crazy with this on the steam deck. NetworkManager kept creating a resolv.conf always pointing to 127.0.0.53.
Until I found that SteamOS (arch in disguise) had created a /etc/NetworkManager/conf.d/dns with a
[main]
dns=systemd-resolved
And that was being used instead of my conf file with dns=default
...
Don't forget to add back the resolv.conf:
systemd-resolvwhatever broke after upgrading ubuntu, and it was easier to just switch back to the Thing That Always Worked than to try to figure it out.