Temporary failure in name resolution on Ubuntu server 22.04.3 LTS

[Bo Berglund]

On Tue, 28 Nov 2023 10:43:53 +0100, Oliver Grawert <ogra at ubuntu.com> wrote:

>Hi,
>Am Dienstag, dem 28.11.2023 um 00:35 +0100 schrieb Bo Berglund:
>> 
>> 
>> I just copied the command in the email...
>> But here it is (newsreader split the line) after space added:
>> 
>> $ dpkg-query -W -f='${binary:Package}\n' | grep -E
>> 'ifupdown|netplan|network-manager|resolv'
>> ifupdown
>> libnetplan0:amd64
>> netplan.io
>> resolvconf
>
>so this looks like some release upgrade left ifupdown and resolvconf
>behind, both have been deprecated (and demoted to universe) in favour
>of netplan/systemd-networkd/systemd-resolved some time between the
>16.04 and 18.04 cycle ...
>
>... not sure what to suggest here, you could indeed stay with the old
>stuff but it might become harder and harder over time to get proper
>support answers and OS integration in ubuntu for these pieces is
>degrading with each release ... on the other hand there is surely some
>learning curve for you to do the transition to netplan manually ...
>

So the problem server is on location in the office and was started in 2017 as an
Ubuntu 16 in order to handle OpenVPN connections, then upgraded thrice to now
22. This last was done on my visit some 6-7 weeks ago.
I think that the crucial upgrade was the 16 -> 18 one where the network-manager
should have been introduced, right? But wasn't...

The other server I started in my home back in 2019 as an 18, then upgraded to 20
where it is right now. It serves multiple purposes one of them being a
Subversion backup which is synced nightly to the main SVN server in the office.
And on this I do have a working networkmanager, I believe.

So my question now is if I can just sudo apt install network-manager on the
Ubuntu 20.04 server in the office and it will migrate whatever network settings
there are to itself?

I.e. can I do this install remotely via ssh?


-- 
Bo Berglund
Developer in Sweden