Using Ubuntu 20.04.3 latest update Oct 19th
After the one but last update Oct 10th suddenly I had a problem
resolving DNS. Before the update my /etc/resolv.conf read :
nameserver 127.0.0.53
In my netmanager settings I had/have entered 2 DNS-Server IP adresses of
my ISP : 1xx.2xx.xxx.21 1xx.2xx.xxx.22
the result of command
$ ls -al /etc/resolv.conf
lrwxrwxrwx 1 root root 32 okt 13 14:10 /etc/resolv.conf ->
/run/systemd/resolve/resolv.conf
So I did
$ sudo rm -f /etc/resolv.conf
$ sudo ln -s /run/systemd/resolve/resolv.conf /etc/resolv.conf
Only to find it didn't change anything : the content of new
/etc/resolv.conf after restarting the systemd-resolve service still
reads
nameserver ::1
I managed to complete the updates by repeatedly saving manually an
/etc/resolv.conf file and overwriting the file written by the systemd-
resolve service (workaround). to make certain that people don't doubt my
capacity to read : I DO understand the warning at the top of the file
saying that the file is overwritten regularly.
I manage to maintain a "usable connection" by regularly overwriting the
file /run/systemd/resolve/resolv.conf, with following content
nameserver 1xx.2xx.xxx.21
nameserver 1xx.2xx.xxx.22
until i restart the systemd-resolve service and the file is overwritten
by resolve and it reverts to
nameserver ::1
I also checked the /run/systemd/resolve/stub-resolv.conf file which has
the following content
nameserver 127.0.0.53
options edns0 trust-ad
My question is :
A- How can I make sure that the resolve service writes the correct file
content in /etc/resolv.conf = I do understand that this is a sym-link
B- Where is the parameter file that systemd-resolve uses to produce
/etc/resolv.conf and /run/systemd/resolve/resolv.conf, because it sure
doesn't read the configuration entered in netmanager settings
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1774632
Title:
The symbolic link /etc/resolv.conf points to the wrong file by default
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1774632/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
