Comment 6 for bug 1890903

I think I'll steer away from systemd-resolved

1) it does not favor my primary nameserver (after a switch it'll not switch back, but continue any failover server)
2) in the end it can even use a nameserver which I have not provided (which is set by the packagebuilder)

Reading into some threads on systemd-resolved it is clear all nameservers are expected equal. This is clearly not the case with small business (or any business, if you ask me).

The uncontrolled usage of the external nameserver set by the packagebuilder is also a weird choice.

These choices might be OK in certain situations (e.g. a laptop to access the web for the wife), but clearly fails my needs.

To change to something else, seel (e.g.):
      https://askubuntu.com/questions/907246/how-to-disable-systemd-resolved-in-ubuntu

(probably this is the cause of some nameserver issue I reported on docker, where docker clients ended up using 8.8.8.8)