Also, systemd-resolved does not have an equivalent of dnsmasq's "all-servers" option, which I need. And because of this bug, I can't run dnsmasq instead of systemd-resolved. I have been able to get something working with both systemd-resolved and dnsmasq running, but having two local dns resolvers is unnecessarily redundant, and more complicated than if I could just run dnsmasq.
> If you know of specific problems with it, we can best help you (and all other Ubuntu users) if you give us bug reports for those problems.
There's this: https:/ /github. com/systemd/ systemd/ issues/ 5755
Also, systemd-resolved does not have an equivalent of dnsmasq's "all-servers" option, which I need. And because of this bug, I can't run dnsmasq instead of systemd-resolved. I have been able to get something working with both systemd-resolved and dnsmasq running, but having two local dns resolvers is unnecessarily redundant, and more complicated than if I could just run dnsmasq.
See my comments on https:/ /bugs.launchpad .net/ubuntu/ +source/ systemd/ +bug/1745463