[Touch-packages] [Bug 1991658] Re: 22.04 upgrade left DNS broken, resolv.conf pointing at resolvconf

2022-12-03 Thread Launchpad Bug Tracker
[Expired for systemd (Ubuntu) because there has been no activity for 60 days.] ** Changed in: systemd (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu.

[Touch-packages] [Bug 1991658] Re: 22.04 upgrade left DNS broken, resolv.conf pointing at resolvconf

2022-10-04 Thread Smylers
I'm pretty sure it was set up however Ubuntu 16.04 installed it, followed by any changes made by the 16.04–18.04 and 18.04–20.04 upgrades. Those first 2 upgrade were seamless in terms of the networking working, so either they didn't make any changes or they updated things automatically as

[Touch-packages] [Bug 1991658] Re: 22.04 upgrade left DNS broken, resolv.conf pointing at resolvconf

2022-10-04 Thread Nick Rosbrook
I think systemd-resolved should have already been managing /etc/resolv.conf on 20.04. Did you disable it on your server before? Can you provide more context on how exactly your DNS was configured before the upgrade? ** Changed in: systemd (Ubuntu) Status: New => Incomplete -- You

[Touch-packages] [Bug 1991658] Re: 22.04 upgrade left DNS broken, resolv.conf pointing at resolvconf

2022-10-04 Thread Nick Rosbrook
** Package changed: ubuntu-release-upgrader (Ubuntu) => systemd (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1991658 Title: 22.04 upgrade left DNS broken,