[Touch-packages] [Bug 1853164] Re: systemd: /etc/dhcp/dhclient-enter-hooks.d/resolved error

2021-06-29 Thread Thayne
> 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

[Touch-packages] [Bug 1745463] Re: Disabling systemd-resolved breaks dhclient resolvconf integration

2019-12-10 Thread Thayne
In this systemd github issue https://github.com/systemd/systemd/issues/5755 in particular is problematic darkstar states "the DNS servers are supposed to be exactly equivalent". But as far as I can tell systemd doesn't have any provision for temporarily falling back to a different nameserver if

[Touch-packages] [Bug 1745463] Re: Disabling systemd-resolved breaks dhclient resolvconf integration

2019-11-26 Thread Thayne
> Can you help me understand the motivation underlying the requirement? The motivation is that if the current dns server goes down, we don't have to wait for the request to timeout and make another request to the next server. Before resolved this was more of a problem since libc would always try

[Touch-packages] [Bug 1745463] Re: Disabling systemd-resolved breaks dhclient resolvconf integration

2019-11-26 Thread Thayne
> If there are scenarios where it is not appropriate to run resolved, then we should absolutely evaluate those and determine how they should be supported in Ubuntu. Maybe there is a better way to do this, but here is my situation. I need to be able to send DNS queries to multiple dns servers