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
OS Ubuntu 20.04.3 LTS
After a recent update a working laptop suddently developped the following
problem :
- DNS problems for al Internet related apps
- Ping : termporary failure in Name resolution
editing manually allows internet access for short term until systemd-resolve
overwrites the
Sorry typo in my previous message ; it should read
I tried overwriting /run/systemd/resolve/resolv.conf with the correct
nameservers and then applied your solution :
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
ALSO AFFECTS DOCKER VPS - Is there a definitive solution? Im going to
try @jasdenty solution. Im not that technical user.
It affects my VPS after "apt upgrade". Suddenly resolving domains from
docker containers stopped - from what i understand docker defaultly
inherits /etc/resolv.conf.
OS: Ubuntu 18.04 bionic
Kernel: x86_64 Linux 4.19.17
For those who encounter situations otherwise, here is my case and
workarounds.
my case:
---
/etc/resolv.conf -> ../run/systemd/resolve/stub-resolv.conf
I remove the symlink and assign a new one
/etc/resolv.conf ->
I have been encountering this issue for the past month on my newly
installed (1-2 months old) version of Ubuntu 20.04.2 LTS.
I finally got frustrated enough to dig in and find a solution and
arrived here from a stackexchange comment.
FYI is all - OP's solution seems to have fixed the issue for
Please disregard my last comment (#5). The problem I had was not this
one but related to using other connector agents in addition to
NetworkManager, in my case the openvpn3 command line.
(Automatic connection to the VPN is not there, but that is probably
safest.)
--
You received this bug
I just want to confirm that this is a problem. I have had it for a
while and not found another workaround (until now) than restarting the
machine.
If this is NOT a bug then something "close by" is a bug.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
I just ran into this issue myself on 20.04. Specifically I was adding my
own internal nameserver to a vm.
@Ubfan, why is stub-resolv.conf the correct file?
The file that /etc/systemd/resolved.conf updates is
/run/systemd/resolve/resolv.conf. As far as I can tell, the proper way
to update
The link target, stub-resolv.conf is the correct file for enabling
systemd-resolvd. Various problems with the systemd-resolvd may be fixed
by installing the libnss-resolve package (bug 1769016). Blank local
domain problems have their own bug, 1699660 (fix is to use ~.). This
report probably
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: systemd (Ubuntu)
Status: New => Confirmed
--
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:
11 matches
Mail list logo
