A solution I found, with much help from Telegram "Linux for Everyone" people is relatively simple. The details are in https://x.com/i/grok/share/scmM5yZrHm8LakpNnWAS6zD1K .
Basically, the commands for ethernet are:
{to find the name of the ethernet connection}
nmcli connection show
{to add specific nameserver connections to resolv.conf}
sudo nmcli con mod "connection name from first command" ipv4.dns "8.8.8.8 8.8.4.4 1.1.1.1"
{to stop overwriting the last statement}
sudo nmcli con mod "connection name from first command" ipv4.ignore-auto-dns yes
{make the changes without a reboot}
sudo nmcli con down "connection from the first command" && sudo nmcli con up "connection from the first command"
{check the resolv.conf file to determine if the changes have been made}
cat /etc/resolv.conf
This was sustained through a reboot.
Didn't see this when it was added.
The above won't help. In order to be able to reach those DNS servers you need a working IP network, a suitable default route, one of the machines concerned configured to NAT traffic to/from the other, and (rather obviously) an internet connection on that machine.
Without all of that you can set the DNS servers to anything you like but it still won't work. Sustained through a reboot or not.
Using public DNS servers also won't resolve the hostnames of machines on your local network.
Statistics: Posted by thagrol — Thu May 22, 2025 12:05 am