Temporary failure in name resolution on Ubuntu server 22.04.3 LTS

[Bo Berglund]

On Sun, 26 Nov 2023 11:27:44 +0100, Oliver Grawert <ogra at ubuntu.com> wrote:

>Hi,
>
>Am Sonntag, dem 26.11.2023 um 11:14 +0100 schrieb Bo Berglund:
>> Why in the world have the Ubuntu maintainers put that comment about
>> NOT editing
>> teh file there???????
>
>This is clearly a bug, the command was changed by upstream systemd to
>be:
>
>resolvectl status
>
>but apparently the text in the generated file (which gets freshly
>generated each boot, thus the warning) has not been adjusted to this
>new command ... you should file it with "ubuntu-bug systemd" ...
>
>ciao
>	oli

So does this mean I will lose the 8.8.8.8 and 8.8.4.4 DNS servers on next
reboot?
I.e. will my edits be removed then?
If it will be romoved on next boot then how can I make it persistent?

-----  later after testing  ----

I did a sudo apt update && sudo apt full-upgrade with the google servers active
and now a lot more data was retrieved and the upgrade process took a lot longer
than when I did it an hour ago...

So previously apt did not manage to get all of its stuff when the DNS was
broken!

After this big apt upgrade I rebooted the server again and now my DNS edits are
all gone!

So I am back at getting the "Temporary failure" error!


****** HELP! ******

How can I get the DNS working properly now?

I have had to edit the hosts file to re-enable the specific setting for
accessing my report server, but nothing else seems to work properly towards the
Internet!

To me it seems like the dist-upgrade from 20.04.6 LTS to 22.04.3 LTS back in
october has broken the system in some strange way that has not shown up until a
few days ago.
This server started as a 16.04 and has been ugraded three times to the current
state.



-- 
Bo Berglund
Developer in Sweden