There seem to be a number of workarounds on the Web, and most of them revolve around modifying either the netplan config file or the systemd resolver config. None really worked for me -- usually, the resolver configuration did not survive a reboot.
I found a very unclean (but effective) workaround by restoring the old functionality of /etc/resolv.conf:
1. Remove the symlink /etc/resolv.conf
2. Create a new /etc/resolv.conf and enter your name servers and search domains.
3. Make this file immutable (chattr +i /etc/resolv.conf)
4. Wait until this bug is resolved
And yes, I am aware that this workaround is *very* ugly. This workaround is (hopefully) temporary, but it seems to me that netplan needs to be fixed first.
There seem to be a number of workarounds on the Web, and most of them revolve around modifying either the netplan config file or the systemd resolver config. None really worked for me -- usually, the resolver configuration did not survive a reboot.
I found a very unclean (but effective) workaround by restoring the old functionality of /etc/resolv.conf:
1. Remove the symlink /etc/resolv.conf
2. Create a new /etc/resolv.conf and enter your name servers and search domains.
3. Make this file immutable (chattr +i /etc/resolv.conf)
4. Wait until this bug is resolved
And yes, I am aware that this workaround is *very* ugly. This workaround is (hopefully) temporary, but it seems to me that netplan needs to be fixed first.