systemd-resolve/NetworkManager changes (17.10 -> 18.04)

[Tom H]

On Mon, May 21, 2018 at 11:26 AM, Liam Proven <lproven at gmail.com> wrote:
> On Sat, 19 May 2018 at 21:02, Teresa e Junior <teresaejunior at gmail.com>
> wrote:
>>
>> How can I restore the old behaviour, or what is the preferred method now?
>
> I had something similar last year. I think the steps here sorted it:
>
> https://askubuntu.com/questions/965527/dns-problems-after-upgrading-from-16-04-to-17-10-how-to-reset-the-dns-settings

Regarding the unbound solution:

1) Replacing the resolved stub resolver with the unbound caching
resolver's a relatively big change.

2) I'd add a check to the target of the "/etc/resolv.conf" to the
procedure; or I'd simply turn it into a one-line regular file (
"nameserver 127.0.0.1" ).